LocalLink 82 (BaltimoreLink)
shuttle route operated by the Maryland Transit Administration

LocalLink 82, formerly Route 97 is a bus route operated by the Maryland Transit Administration in Baltimore. The bus route was formerly operated as a shuttle service, known as the Mondawmin Shuttle Bug or Mondawmin Shuttle, as one of two neighborhood shuttle routes operated by the Maryland Transit Administration in Baltimore. It was the second and is so far the final in the series of shuttle bus routes to be introduced by MTA in the 2000s. The route serves Baltimore City Community College, Coppin State University, and various nearby streets.
The route formerly had the "shuttle" status, operating via a circuitous route, and allowing boarding for a reduced $1.00 fare.
History
LocalLink 82 began service under Route 97 in 2002.
In 2005, as part of the Greater Baltimore Bus Initiative, it was initially proposed that the shuttle's frequency would be reduced to one bus an hour, and riders were encouraged to use other regular bus routes that shared common routing. However, after community meetings, it was ultimately decided that the schedule would remain the same.
In 2006, MTA proposed that the route would be modified to serve Reservoir Hill in order to replace a portion of Route 5 that was at the time proposed for modification away from this area. But it was later decided that Route 5 would continue to serve Reservoir Hill.
The public source identifies “LocalLink 82 (BaltimoreLink)” as shuttle route operated by the Maryland Transit Administration. This brief keeps that definition visible, then builds a research path around LocalLink, BaltimoreLink and shuttle.
Why this record matters
A short description can identify a subject without explaining its stakes. For “LocalLink 82 (BaltimoreLink)”, the useful work is to connect “shuttle route operated by the Maryland Transit Administration” to the records capable of establishing context and consequence.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jun 16, 2026. The linked authority identifier is Q7371547. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2002, 2005 and 2006.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “LocalLink 82 (BaltimoreLink)”, its source revision and the description used here.
- Expand the search: follow LocalLink 82 (BaltimoreLink) primary sources, LocalLink 82 (BaltimoreLink) archive and LocalLink research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “LocalLink 82 (BaltimoreLink)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “LocalLink 82 (BaltimoreLink)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.