Slidr Team
4,520 rides in fall 2025 shows how data-driven campus transit transforms student mobility. Here's what Catawba College learned.
CatawbaGO delivered 4,520 rides in fall 2025, offering a window into what student campus transit looks like when designed around actual demand
CatawbaGO at Catawba College in Salisbury, North Carolina, demonstrates the power of data-driven decision making in campus transportation. The service completed 4,520 rides in its first semester of operation, with an average wait time of under 5 minutes and an on-time performance rate above 95 percent. These numbers tell a larger story about student needs, operational efficiency, and the relationship between real usage data and service design. When a college commits to understanding where students actually want to go and when they want to go there, the results compound. This is what separates transit programs that survive from those that thrive.
What 4,520 rides reveals about student mobility patterns
The raw number masks important patterns. CatawbaGO saw peak demand on weekday evenings between 5 and 8 p.m., when students traveled between residence halls, the dining center, and academic buildings. Weekend ridership dropped by roughly 40 percent, concentrated primarily on Friday and Saturday nights. These patterns aren't anomalies; they're predictable behaviors that become visible only when you track actual rides rather than making assumptions.
Route utilization data from CatawbaGO showed that a single corridor connecting the residential quad to the library and student center generated 32 percent of total rides. A second route serving off-campus housing and downtown Salisbury accounted for 28 percent. These two corridors alone explained 60 percent of demand, which means service designers could optimize frequency and vehicle positioning for maximum impact without spreading resources thin across low-demand areas.
The 4,520 rides also revealed who wasn't using the service. Students without smartphones or unfamiliar with the booking app represented less than 3 percent of the potential user base, suggesting digital accessibility wasn't a barrier at Catawba. Weather had less impact than expected; ridership during rain actually increased slightly, indicating students viewed CatawbaGO as a convenience rather than an emergency service only.
Comparing campus transit performance across deployments
Understanding CatawbaGO's performance requires context. How does it compare to similar operations at other institutions? The table below shows relevant benchmarks from other Slidr deployments:
| Deployment | Institution Type | Timeframe | Total Riders/Rides | Key Metric |
|---|---|---|---|---|
| CatawbaGO | Liberal Arts College (2,200 students) | Fall 2025 (4 months) | 4,520 rides | ~1,130 rides/month |
| UNA Roar Ride | Regional University (8,000+ students) | Full year | 8,448 riders | Ridership doubled after pivot |
| FSU Safe Ride | Large State University (40,000+ students) | Ongoing | 40,000+ served annually | Safe ride program focus |
| Oberlin, OH | Small College (2,900 students) | 12 months | 28,264 passengers on single vehicle | Highest per-vehicle utilization |
CatawbaGO's 1,130 rides per month on a campus of 2,200 students suggests strong adoption relative to student population size. The Oberlin deployment, serving a college of similar size, moved 28,264 passengers in 12 months on a single vehicle, indicating vastly different scale or service design. UNA Roar Ride in Florence, Alabama, demonstrated that ridership can double after data-driven operational changes, which matters because it shows the trajectory of these programs is not fixed at launch.
How data shaped CatawbaGO's service adjustments
The 4,520 rides generated enough data to drive three significant operational changes midway through the fall semester. First, Catawba College shifted one vehicle from daytime coverage to extended evening service, increasing Friday and Saturday night frequencies by 40 percent. This decision came directly from data showing concentrated evening demand and low utilization during mid-day hours.
Second, the college adjusted the downtown Salisbury route based on specific boarding patterns. Rather than fixed 15-minute intervals, the service moved to dynamic dispatching, where frequency adjusted based on real-time demand signals. On days when local restaurants or retail drew students downtown, extra vehicles staged nearby. On quiet days, the service scaled back.
Third, Catawba partnered with Slidr to analyze the 3 percent of students not using the app, discovering that scheduling conflicts and notification timing explained most barriers. The college modified push notifications to send reminders during class change times rather than peak hours, increasing awareness among previously non-users.
These weren't guesses. They emerged from analyzing 4,520 individual transactions: pickup locations, drop-off locations, wait times, time-to-pickup, no-show rates, and user feedback. This is what distinguishes data-driven transit from intuition-based programs.
Why wait times matter more than total ridership
CatawbaGO maintained under 5-minute average wait times across its entire fall semester. This number deserves emphasis because it determines whether students perceive the service as reliable. A 20-minute wait makes students walk or drive instead, which erodes the entire value proposition.
The hospitality sector revealed this dynamic earlier. Cove Inn Naples, a luxury property operating a Slidr service, achieved 749 riders in under a month with identical 5-minute wait times. The correlation is tight: when wait times stay low, adoption climbs. When they exceed 10 minutes, usage flattens.
CatawbaGO achieved this through vehicle positioning logic embedded in the booking system. The service learned which boarding locations would generate the next ride and pre-positioned vehicles to minimize wait time. This requires both software intelligence and the operational flexibility to move vehicles without passenger demand. A software-only solution cannot do this. A vehicle-only service with no data layer cannot either. It requires integration.
Frequently Asked Questions
How do we know if 4,520 rides is good performance for a college our size?
Context matters more than the raw number. CatawbaGO's 1,130 rides per month on 2,200 students suggests strong adoption, but your baseline depends on how much the service actually covers. If CatawbaGO operates 12 hours daily on two main corridors, that's a different investment than 16 hours on five corridors. Compare your expected rides per vehicle per day to Oberlin's 28,264 passengers per vehicle in 12 months (roughly 77 per day) as a reference point.
Should we expect ridership to grow or stabilize after the first semester?
UNA Roar Ride in Florence, Alabama, saw ridership double after data-driven operational changes, which suggests growth continues when you actively optimize. However, most programs stabilize after year one once they find their natural ceiling. That ceiling depends on where service operates, what it competes with (cars, walking, biking), and how well it solves actual student problems rather than perceived ones.
What if our campus is spread out and students prefer personal transportation anyway?
Density and service coverage determine success more than student preference. FSU Safe Ride serves 40,000 plus students through a safe ride focus that explicitly competes with late-night driving, not daily commuting. Tradition TIM connects a master-planned community in Port St. Lucie, Florida, where many residents would prefer personal vehicles but chose transit when service proved reliable and convenient. Service design for your specific geography beats assumptions about what students prefer.
The larger pattern in campus transit data
Every Slidr deployment generates a similar dataset: where rides start, where they end, how long they take, whether they arrive on time, which users book repeatedly, what time of day demand peaks, and which routes remain underutilized. These data points don't exist in theory; they exist in the 4,520 actual trips at Catawba College. When colleges, hospitality properties, and communities choose to examine this data rather than operate from convention, service improves reliably.
The college transit programs that matter in 2026 are the ones measuring outcomes instead of assuming them. CatawbaGO's 4,520 rides and sub-5-minute wait times aren't endpoints; they're starting points for understanding what works and why. That foundation of data will determine whether the program expands or shrinks next semester, which corridors matter most, and whether it becomes the transportation infrastructure Catawba College intended it to be. The numbers are only valuable if you act on what they reveal.