Post by Uchechukwu Eze

Train journeys are not just movements from one station to another. They are signals. Signals about passenger behavior, pricing pressure, route demand, service reliability, and where rail operators may be losing revenue or customer trust. In this work, Rail Revenue Intelligence: Analyzing UK Train Ticket Demand and Pricing, I analyzed mock National Rail ticket data from January to April 2024 to understand how UK train rides perform across ticket type, ticket class, route, payment method, journey time, delays, cancellations, and revenue. A few insights stood out: 🚆 Manchester Piccadilly led in trip activity, followed by London Euston, while Bristol Temple Meads recorded the weakest activity. 🎟️ Advance tickets were the most purchased, showing that passengers are highly price-conscious and prefer early-booking savings. 💳 Credit card payments dominated, accounting for over 61% of all transactions. ⏰ Demand was concentrated around commute periods, with strong peaks at 6 AM and 6 PM. 💷 Prices were not flat across the day. The highest average ticket price appeared around 8 AM, pointing to stronger peak-hour pricing pressure. ✅ Most trips arrived on time, which is encouraging. But delay risk still matters, especially with weather and signal failure appearing as key disruption drivers after cleaning the missing delay reasons. The biggest business lesson from this project is simple: Rail operators should not treat pricing, demand, delays, and route performance as separate problems. They are connected. If demand peaks at specific hours, scheduling should respond. If Advance tickets dominate, pricing strategy should reflect customer sensitivity. If certain routes carry more demand, capacity planning should prioritize them. If delays are linked to weather and signal failures, prevention should be operationally targeted. This project reminded me that data analytics is not just about charts. It is about helping businesses see what is working, what is underperforming, and where better decisions can improve both revenue and customer experience. Tools used: Python, Pandas, Matplotlib, Seaborn #DataAnalytics #Python #BusinessIntelligence #RailAnalytics #TransportAnalytics #EDA #DataVisualization #Pandas #Seaborn #RevenueAnalytics #PublicTransport #DataScience [14]