<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: N Patkai</title>
    <description>The latest articles on Forem by N Patkai (@userium).</description>
    <link>https://forem.com/userium</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3844059%2Fb8e18b1d-75f8-43f6-8117-d7a241b67ba3.png</url>
      <title>Forem: N Patkai</title>
      <link>https://forem.com/userium</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/userium"/>
    <language>en</language>
    <item>
      <title>We Logged 341 EV Charging Sessions. 4 in 10 Had Problems.</title>
      <dc:creator>N Patkai</dc:creator>
      <pubDate>Thu, 26 Mar 2026 05:20:27 +0000</pubDate>
      <link>https://forem.com/userium/we-logged-341-ev-charging-sessions-4-in-10-had-problems-17cj</link>
      <guid>https://forem.com/userium/we-logged-341-ev-charging-sessions-4-in-10-had-problems-17cj</guid>
      <description>&lt;p&gt;We built &lt;a href="https://www.evcourse.com" rel="noopener noreferrer"&gt;EVcourse&lt;/a&gt;, an app that helps drivers troubleshoot EV charging problems. One feature lets drivers log how each public charging session went: good, okay, or bad.&lt;/p&gt;

&lt;p&gt;Between February and March 2026, 72 drivers logged 341 sessions across Finland, Germany, and the UK. This is what we found.&lt;/p&gt;

&lt;h2&gt;
  
  
  The headline number
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;39% of public charging sessions had some kind of problem.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;60.7% rated good (207 sessions)&lt;/li&gt;
&lt;li&gt;24.6% rated okay (84 sessions)&lt;/li&gt;
&lt;li&gt;14.7% rated bad (50 sessions)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The 7 most common problems
&lt;/h2&gt;

&lt;p&gt;Drivers who rated a session okay or bad picked up to two reasons. Here's how often each came up:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;#&lt;/th&gt;
&lt;th&gt;Problem&lt;/th&gt;
&lt;th&gt;% of all reasons&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Charging too slow&lt;/td&gt;
&lt;td&gt;20.0%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Charger not working&lt;/td&gt;
&lt;td&gt;17.8%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Payment failed&lt;/td&gt;
&lt;td&gt;13.0%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;No available charger&lt;/td&gt;
&lt;td&gt;9.7%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Session stopped unexpectedly&lt;/td&gt;
&lt;td&gt;8.1%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Cost higher than expected&lt;/td&gt;
&lt;td&gt;7.0%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Confusing interface&lt;/td&gt;
&lt;td&gt;5.9%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Also reported: wrong connector (4.9%), app issue (4.3%), long queue (3.2%), heavy cable (2.2%), felt unsafe (1.6%), bad weather (1.1%).&lt;/p&gt;

&lt;h2&gt;
  
  
  What surprised us
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Slow charging was #1, not broken chargers.&lt;/strong&gt; Most drivers expected faster speeds than they got. This is often explainable (battery&lt;br&gt;
temperature, state of charge above 80%, shared power between stalls), but charger screens rarely explain why.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Payment failures at 13%.&lt;/strong&gt; In 2026. Many of these were app authentication issues, not card declines.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Confusing interface" at 5.9%.&lt;/strong&gt; The charger worked, the driver just couldn't figure out what the screen was telling them. &lt;/p&gt;

&lt;h2&gt;
  
  
  Caveats
&lt;/h2&gt;

&lt;p&gt;341 sessions from 72 drivers is a small sample. We're not pretending this is definitive European research. Organizations like &lt;a href="https://www.transportenvironment.org/" rel="noopener noreferrer"&gt;Transport &amp;amp; Environment&lt;/a&gt; and the &lt;a href="https://alternative-fuels-observatory.ec.europa.eu/" rel="noopener noreferrer"&gt;EU Alternative Fuels Observatory&lt;/a&gt; track charging infrastructure at much larger scale.&lt;/p&gt;

&lt;p&gt;But this is real data from real sessions, not a survey asking people to remember. Drivers logged each session right after it happened. &lt;/p&gt;

&lt;p&gt;As more drivers use the app, this dataset grows. We plan to update the numbers regularly, if you're interested?&lt;/p&gt;

&lt;h2&gt;
  
  
  The full report
&lt;/h2&gt;

&lt;p&gt;The complete report is on our site:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.evcourse.com/ev-charging-reliability-europe" rel="noopener noreferrer"&gt;EVcourse EV Charging Reliability Report&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we're sharing this
&lt;/h2&gt;

&lt;p&gt;Telematics systems tell fleet managers the car charged from 20% to 80%. They don't say the driver spent 10 minutes figuring out the&lt;br&gt;
payment screen, or that the first charger was broken.&lt;/p&gt;

&lt;p&gt;We think this human data layer is missing from the EV charging conversation. If you have any questions, email us at &lt;a href="mailto:nina@evcourse.com"&gt;nina@evcourse.com&lt;/a&gt; &lt;/p&gt;




&lt;p&gt;&lt;em&gt;Built by EV industry engineers in Finland. &lt;a href="https://www.evcourse.com" rel="noopener noreferrer"&gt;EVcourse&lt;/a&gt; is free to try on iOS. We drive EVs year-round, including through freezing winters with no home charging.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>data</category>
      <category>sustainability</category>
      <category>electricvehicles</category>
      <category>evcharging</category>
    </item>
  </channel>
</rss>
