I would suggest you have a Daily Time Sheet Header Table, with one record per route per day.
Then you have a Route or Stops Table with, in the example above, 5 records for route 106A, one each for each stop. If the route is potentially different each day you may want to include a 'DaysAvailable' field. I'd also include a Sequence Number so you can sort the stops into the correct sequence.
Then if the number of stops is guaranteed to be small you can show the list of stops as a portal on the header record. If it may spill over a page then run the report from the Routes Table. Find all the stops for a route for a day, then have a print layout that pulls in the appropriate header and footer info from the Header Table, and lists the found set of stops.
I would suggest reading the White Paper for FM Novices, it can clarify design considerations.
Sometimes the main focus of a database is not one table or another, but the join table created to pull informaiton from both main tables.
There are even instances of a join table pulling data from two join tables that link data from two main tables.
The White Paper for FMP Novices is useful
Lynda dot com has Filemaker Videos (portions are free)
Free unlocked templates are useful for examining design
Starting Point -
A free calendar is available to be bolted onto your database
You can search specific Filemaker sites on this Custom Google Search
Looking at FMP business database demos is useful - some are fully useable
The Excelisys Business Tracker V3.0
Filemaker released a FMP runtime database in 2007 for students called "Campus Productivity Kit" and is available online, notably at CNet
Google "Campus Productivity Kit"