First Impression
My buddy Mark, who knows I’m obsessed with AV data, told me to ditch TeslaFi’s generic stats and try FSD Hunter. He said it showed actual cars driving right now. I downloaded it on my iPhone 14, paid the $5.99, and opened it up last Monday morning. The map loaded fast, I’ll give it that. But my initial excitement faded fast. In my suburban neighborhood, the map was a ghost town—just one lonely pin from three days ago. I drove downtown, and sure, there were more pins, but half of them were for Teslas just parked. The app calls that a “sighting,” but if the car’s off, how do we know FSD was even active? It felt less like a live intelligence tool and more like a fancy Tesla locator with a hopeful label.
What It Does Well
When you find a legitimate, active sighting, the app shines. The filtering is precise. I can strip out all the parked Model 3s and focus on, say, a Model S reported to be navigating a roundabout. On Wednesday around 5:30 PM, I was on El Camino Real and got an alert for a “Model Y performing lane change maneuvers” two miles ahead. I caught up and watched it handle a complex merge during rush hour. That raw, unfiltered data point is invaluable. The community confirmation system is also smart. When I posted a video of a hesitant FSD car at a four-way stop, another user verified the behavior within an hour, adding notes about the software version. That collaborative verification is something you won’t get from a passive data logger.
Where It Falls Short
This is where my power-user gripes come in. The app is buggy under pressure. Twice, after leaving it running in the background during a long drive, it completely froze my iPhone’s GPS services until I did a hard reboot. That’s unacceptable. The data fields are also too shallow. I want to see the suspected FSD software version, estimated confidence score from the spotter, and maybe even ambient weather conditions for that sighting—all at a glance. Instead, I have to tap into each pin, then sometimes into another menu. It’s clunky. The biggest shortfall is user density. Unless you’re in San Francisco or Austin, the map is so sparse it becomes almost useless for real-time hunting. You’re just reviewing yesterday’s news.
Is It Worth the Price?
For $5.99 as a one-time purchase, it’s a niche gamble. If you live in a Tesla-dense urban core and are fascinated by FSD behavior, you’ll get $6 of entertainment and insight pretty quickly. For me, it has already sparked a few great observations. But if you’re in a lower-adoption area or expect a polished, rock-solid app, you’ll feel short-changed. It’s not a subscription, which I respect, but the trade-off feels like slower update cycles and these persistent bugs. I paid, and I don’t regret it, but I’m also constantly aware of its limitations.
Developer & Support
The solo dev vibe is strong here. The contact is a Startmail address, which tracks. I had an issue where my confirmed sightings weren’t adding to my profile score. I emailed on a Thursday and got a helpful, detailed reply the following Monday. They identified a server-side caching bug and fixed it. The response wasn’t fast, but it was personal and effective. Update notes mention things like “improved pin clustering” and “added brake light status field,” which shows they’re listening to power users. It’s clearly a passion project, not a corporate product. That means direct feedback might get heard, but don’t expect instant, 24/7 customer service.
Privacy & Safety
This is the elephant in the room. The app requires always-on location to be useful, and you’re essentially logging the location of other people’s cars, sometimes with photos. The terms say you shouldn’t photograph license plates or people, and that you must be a passenger, not the driver, when logging. That’s good. But I’ve seen pins dropped clearly from the driver’s seat, and photos with plates barely blurred. The app has a report function, but it feels reactive. I’m careful—I only log from the passenger seat or sidewalk, and I heavily blur any identifying details. The community needs to be better self-policed, and the app could use more prominent, mandatory safety reminders before your first post.
How does FSD Hunter's live tracking and filtering work?
FSD Hunter shows real-time pins on a map for Teslas that users have reported as actively using Full Self-Driving. You can filter out parked cars and focus on specific models or maneuvers, like a Model Y changing lanes, so you only see verified, active FSD behavior.
What is the community confirmation system and how do I use it?
When you spot a car using FSD, you can post a video or description, and other users can verify the behavior, adding details like the software version. This collaborative verification helps confirm that a sighting is genuine, making the data more reliable than passive logs.
Why does FSD Hunter sometimes freeze my iPhone's GPS, and how can I fix it?
The app can bug out if left running in the background during a long drive, freezing GPS services until you hard reboot your phone. To prevent this, try closing the app entirely when you're not actively using it, and make sure your iOS is updated to the latest version.
The map shows many parked Teslas as 'sightings'—how do I avoid false positives?
Use the filtering options to exclude stationary or parked vehicles, and focus on reports with specific maneuvers like lane changes or roundabout navigation. Also, check the community verification status; a sighting confirmed by other users is much more likely to be a genuine FSD test.
How does FSD Hunter compare to TeslaFi for tracking FSD activity?
Unlike TeslaFi, which gives you generic stats from your own car, FSD Hunter shows you real-time, crowdsourced sightings of other Teslas actively using FSD. It's more like a live intelligence tool, but it can be buggy and has fewer data fields than TeslaFi's detailed logs.
