← Back to the map

About this site

Worthing Brighton Bus shows live buses and trains along the Adur, Worthing and Brighton coast, works out what a journey costs in tickets, and sets out a case for better service across the council boundary, which runs through Portslade.

It is independent. It is not run by, funded by, or endorsed by any bus operator, train operator, or council. Operator names, route numbers and liveries appear here to identify services, and that is all they mean. Where the site quotes a fare or a departure count, it says where the figure came from and when it was checked.

Correcting something

If something here is wrong, please say so. A campaign site that gets its facts wrong is worse than no campaign site. The quickest route is to open an issue on the public issue tracker, which is where the project's work happens in the open. Anything posted there is public, so keep personal details out of it.

To report something you think is illegal or harmful (see reporting content), to have something you sent removed, or for anything about your personal information, email privacy@worthingbrightonbus.co.uk instead. It will be taken down.

Privacy and terms

The site sets no cookies, counts visits without them (and you can switch that off), and keeps submissions private until a person has reviewed them. The privacy notice sets out exactly what happens to information about you, who is responsible and your rights. The terms of use cover what the information is and is not, the rules for submissions, and reuse.

Accessibility

The site aims at WCAG 2.2 AA, with 44 px targets and AAA text contrast where it can manage them. Known gaps, stated rather than hidden: the map itself is difficult to operate without a pointer, which is why the live view carries a stop and station search that does the same job from the keyboard. Text size, reduced motion and a colour-blind-safe palette can be changed in the site's accessibility settings, which are also linked from the footer of every page. If something is unusable for you, that is a bug. Please report it on the tracker, or by email, and say what you were trying to do.

Reading live times

On a stop's board, a time with a green dot is live: we can see that bus, and the time is worked out from where it is, or taken from the operator's own prediction. A time without a dot comes from the published timetable, because that bus isn't reporting yet.

Our own estimates take how late a bus was when it last reported its position and assume it stays that late. A bus running early is assumed to wait at its next timing point, because buses may not leave those early. Buses often make up time further along, so an estimate a long way ahead tends to say later than the bus will really come. Be at your stop by the timetabled time. The bus positions arrive a few minutes late, so a stop the bus has probably already passed is shown as passed.

We only estimate for buses that tell us which timetabled journey they are running, about seven in ten. For the others the Bus tab lists the stops ahead with their timetable times, labelled as such.

Where the data comes from

Timetables and live bus positions
The Department for Transport's Bus Open Data Service, rebuilt weekly. Contains public sector information licensed under the Open Government Licence v3.0.
Live departure predictions
Source: http://transportapi.com/
Train times
Realtime Trains, with data from Network Rail and other sources.
Maps
© OpenStreetMap contributors, available under the Open Database Licence.
Council and electoral boundaries
Source: Office for National Statistics licensed under the Open Government Licence v.3.0. Contains OS data © Crown copyright and database right 2026.
Postcode lookups
postcodes.io, using the ONS Postcode Directory. Source: Office for National Statistics licensed under the Open Government Licence v.3.0. Contains OS data © Crown copyright and database right 2026. Contains Royal Mail data © Royal Mail copyright and database right 2026.
Councillors
Names and contact details come from each council's own published member directory and are never derived from a name pattern.
Disruptions
Diversions, closures and stop suspensions as published by operators and councils through the Bus Open Data Service. Shown in their authors' words, with who published them.
Stop letters, streets and landmarks
NaPTAN, the Department for Transport's national register of stops, under the Open Government Licence.

Service comparisons on this site count scheduled departures from the published timetable. That is not the same as buses that actually ran, and a difference in service either side of a boundary is not on its own proof that the boundary caused it. The full method, denominators and caveats are published with the figures.

How journey times are measured

Buses in this area report where they are every minute or so, through the Department for Transport's open data service. We record those reports and work out when each bus passed each stop. Then, for any two stops, we can say how long each tracked journey took between them.

Usually takes
The middle value of every journey we timed between the two stops: half were quicker, half were slower. One bus stuck in traffic cannot move it.
Allow
How long to leave if you need to be on time: only 1 in 10 of the buses we timed took longer. It is only shown once we have timed at least ten, and with fewer than fifty it says exactly how many took longer.
When you travel
Weekdays or weekends, then a time of day: the morning peak (08:00 to 10:00), daytime (10:00 to 16:00), the evening peak (16:00 to 18:00), or early and late, which is everything before 08:00 and after 18:00. Each choice shows its own usual time, and the chart shades it against the rest of the day.
The typical line
The usual journey time hour by hour, drawn only through hours where we timed at least three buses. The slider under the chart describes any hour in words, including how long to allow where we timed at least ten, and a table lists every hour.
The timetable line
What the timetable promised for each departure through the day. We record the timetable every night alongside the buses, so the comparison still holds after the timetable is replaced. Where we have no recorded timetable yet, the line is drawn from the buses we timed, and says so.
How often buses run
Beside each answer, from the timetable: plenty of buses means one every 15 minutes or better, some buses up to every 30 minutes, and only a few buses anything less often. Weekends are judged on Saturdays and Sundays separately, since their timetables differ.
How much it rests on
Each answer says how many buses we timed and over how many days. Where we have timed fewer than ten, it says to treat the times as a rough guide.
What is left out
Journeys where we did not see the bus at both stops, and any whose recorded times run backwards. Coaches are not counted.

Not seeing a journey is not proof that no bus ran: our recordings miss some journeys, and some operators report their buses less reliably than others. Each answer says how many journeys it rests on, and how many the timetable scheduled. Journeys recorded before 23 September 2026 used an earlier and less strict way of telling which bus was which, and the answers say how many of those they include.

Licences and credits

The site's code is under the MIT licence, and its own written content and data under Creative Commons Attribution 4.0. Neither covers material that belongs to others. Third-party licences are listed in THIRD_PARTY_NOTICES.md, and what this site owns versus what it borrows is recorded in the asset rights register.