Race complete

Verdant Ride Time Trials

Thursday, September 3, 2026 at 4:30 pm

Little Carnelian Lake, MN

Half mile courseCustomPublic raceEvent ID verdant-ride-time-trials-little-carnelian-2026-09-02

WhenThursday, September 3, 2026 at 4:30 pm

WhereLittle Carnelian Lake, MNLog in for directions

Field4 of 8 spots open

Event HostVerdant Ride, with PosterduckLog in and register to get the Host’s contact details.

The course

Custom

A custom layout set by the Event Host. Check the notes below for the buoy order and anything unusual about this water.

Half a mile total. Four yellow turn buoys with buoy 4 farthest out, two green gate buoys 8 to 12 ft apart. Three runs each, best single time counts.

How courses are built

Verdant Ride took the race on adjusted time at 41.02s. Fastest raw run: Verdant Ride at 41.02s. Runs were timed frame-accurately from video at the gate.

Notes from the Host

The weather cleared so we are still a go for today's race! Looking forward to see you!

Drive your gear down to the lake, past the house. If you don't see a lake, you've not gone far enough.

Final results

Timed frame-accurately from video at the gate, to the hundredth of a second.

#	Rider	Run 1	Run 2	Run 3	Best	Adjusted
1	Verdant Ride	41.21s	41.02s	45.19s	41.02s	41.02s
2	Posterduck	45.64s	45.33s	44.67s	44.67s	44.67s
—	AlienAllen	—	—	—	—	—
—	Mr. Ride	—	—	—	—	—

Post race review

Every counting run at this race was judged from frames at the gate, and the pictures are here. Sign in to see them.

Who is attending

7 riders are in. Log in to see who is riding, and to put your own name down.

Race chatter

Questions about launch access, ride sharing, spare gear, or trash talk. Everyone racing can post below.

More racing nearbyeFoil races in Minnesota·eFoil races in United States

Comments

One response to “Verdant Ride Time Trials”

Mr. Ride
September 4, 2026
System Analysis: Verdant Ride vs Posterduck, Little Carnelian
Verdant Ride Posterduck
Runs 8 5
Fastest 41.02 44.67
Best three 41.02 / 41.21 / 42.61 44.67 / 44.77 / 45.33
Best-three average 41.61 44.92
Spread, fastest to slowest 4.17 s 0.98 s
VR took it by 3.65 seconds on the single best lap and 3.31 on the three-lap average, about 7.4 percent. But look at PD’s spread. Five runs inside 0.98 of a second, standard deviation 0.47. That is metronomic. VR was the faster rider and he was the more repeatable one by a factor of three, which is a genuinely different racing profile and makes for a better rivalry than the gap suggests.
VR’s session tells a story too. VR opened 41.21 and 41.02, then drifted to 45.19, then settled into a tight 42.6 to 43.8 band for the last five. VR’s two fastest laps were the first two.
On the timing itself: 13 runs, 13 clean. Every one autoGate: true, how: video_frame, 30 fps, and officialTimeMs matching the recorded time exactly on all thirteen. No manual entries, no corrections. Worth saying plainly since the run-to-run gaps look impossibly tight if you read them wrong: those stamps are when they were assigned each lap to a rider, not when it was ridden. The system is as efficient as it was designed with all thirteen assigned in under three minutes.
Two small things I noticed, neither of which affected a result:
VR’s very first run, the 41.21, is the only one of the thirteen with no start or finish photo. Every other run has both. That is almost certainly the photo-saving bug I confirmed in the API earlier tonight, where two frames landing at once can drop one. First real evidence of it costing something you can actually see.
Log in to Reply