ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Notitia Dignitatum and the Saxon Shore Forts

Updated on May 26, 2012
Click thumbnail to view full-size
The remains of the walls at the Roman fort at Portchester, ancient Portus Adurni.The ruins of the Roman fort at Richborough, named as Rutupiae and as part of the Saxon Shore forts.Ruins of the Roman fort at Richborough. (Ruptiae)
The remains of the walls at the Roman fort at Portchester, ancient Portus Adurni.
The remains of the walls at the Roman fort at Portchester, ancient Portus Adurni. | Source
The ruins of the Roman fort at Richborough, named as Rutupiae and as part of the Saxon Shore forts.
The ruins of the Roman fort at Richborough, named as Rutupiae and as part of the Saxon Shore forts. | Source
Ruins of the Roman fort at Richborough. (Ruptiae)
Ruins of the Roman fort at Richborough. (Ruptiae) | Source

Origin of the Saxon Shore

The Saxon Shore as it existed in Britannia and Gaul functioned as a network of fortifications to guard against the incursions of barbarian forces. For the first 200 years of Roman Britain (50 A.D. - 250 A.D.) the main threat resided in the north of Britain, home of the Caledonian tribes. The walls known as Hadrian's Wall and the Antonine Wall were constructed to serve as the main defense against the Caledonian tribes. They functioned as more than simply defensive walls, but the point is that the north was the hotspot for Rome's military activity in Britain. That trend began to change in the 3th century.

The mid-3rd century saw an influx in the number and frequency of sea-based invasions in the south of Britain. The Saxons, Vikings and Danes all began to move west because of the intense pressure they faced from the Huns in the east. Their sea-going prowess made southern Britain an ideal target for their invasions, especially since southern Britain did not possess a defensive network as did northern Britain. The Saxon Shore, then, was built to help guard against the growing tensions of the 3rd century.

Timeframe of the Saxon Shore's Construction

Many times the Saxon Shore is viewed as a functioning whole, a network of coastal forts. In reality, each fort was constructed separately over a period spanning almost 100 years. It was not until the last few were being built that Rome began to consider the forts as a whole. The earliest of the Saxon Shore forts were built around the 210's A.D, while many of the later forts were not begun until the 270's to 280's A.D. In addition to the forts that were purpose-built for the Saxon Shore, the fort at Dubris (modern-day Dover) was built in place of a Roman mansio that had stood since the initial Roman invasion.

An illustration of the nine Saxon Shore forts in Britannia, taken from a 16th century version of the "Notitia Dignitatum."
An illustration of the nine Saxon Shore forts in Britannia, taken from a 16th century version of the "Notitia Dignitatum." | Source

The Notitia Dignitatum

The only contemporary source for the history of the Saxon Shore can be found in a 5th century Roman document known as the Notitia Dignitatum. The Notitia is a unique document that lists most of the existing imperial offices and their functions within the Roman Empire. It mentions the Saxon Shore as a command of a Roman official known as the Comes Litoris Saxonici per Britanniam or "the Count of the Saxon Shore in Britannia."

This Count was the official granted charge of the Saxon Shore forts in Britannia, nine of which are subsequently listed in the Notitia. Undoubtedly, the Saxon Shore consisted of several forts in addition to those listed, as well as the forts that guarded the northwestern shore of Gaul.

The Forts of the Saxon Shore

Regulbium and Branodunum

Two of the earliest forts of the Saxon Shore were named Regulbium and Branodunum. Both of the early forts were built in a rectangular layout common to fortifications, a layout known as the castrum. Both forts were built in positions from which they could guard important river estuaries opening on the English Channel, prime targets for the barbarian invaders of the 3rd century.

Rutupiae

The site of the fort at Rutupiae is today known as Richborough Castle. This site was the location of a Roman fort since the first Roman landing in Britain in 43 A.D. Over the years, the fort was expanded and reinforced so that by the Saxon Shore era of the late 3rd century it was reconstructed into a substantial fort covering almost 5 acres. Many historians believe that Rutipiae was largely constructed during the reign of the usurper Carausius.

Click thumbnail to view full-size
A view from the tower of Portchester Castle, looking down on the walls built for the 3rd century Roman fort.Remains of the Saxon Shore fort now known as Burgh Castle.
A view from the tower of Portchester Castle, looking down on the walls built for the 3rd century Roman fort.
A view from the tower of Portchester Castle, looking down on the walls built for the 3rd century Roman fort. | Source
Remains of the Saxon Shore fort now known as Burgh Castle.
Remains of the Saxon Shore fort now known as Burgh Castle. | Source

Portus Adurni

The name Portus Adurni only appears in the Notitia, but the common belief is that the Roman fort at Portchester is the fort being referenced. This fort was built sometime in the 3rd century as protection for Portchester Harbor. Portus Adurni has weathered the centuries with remarkable resiliency, and is one of a very few Roman era forts to have survived with its walls largely intact.

Portus Lemanis

The remains of the fort at Portus Lemanis have suffered ruin because of the ground on which the fort was constructed. When the fort was constructed in the 3rd century, it overlooked a harbor, as did many of the Saxon Shore forts. The harbor has filled with silt during the intervening years, and the fort is largely disappeared thanks to its foundation of clay.

Gariannonum

The Saxon Shore fort at Gariannonum was also built during the late 3rd century. This site has been the subject of some dispute as it lies directly across a river estuary from another Roman fort. The debate focuses on which fort is the one that was mentioned in the Notitia, since both forts bear similar Roman names and locations. The majority of historians seem to believe that the Roman fort of Gariannonum is synonymous with the modern-day Burgh Castle.

A map of the Saxon Shore forts as they stood in the late 3rd century.
A map of the Saxon Shore forts as they stood in the late 3rd century. | Source

Othona

The Saxon Shore fort at Othona was another of the forts constructed during the 270's to 280's. Its location on the tip of the Dengie Peninsula made it an ideal defense for the river estuaries of two rivers, the Blackwater and the Colne. The river Colne led to the important Roman city of Camulodunum, a trade center that had become quite wealthy by the late 3rd century.

Dubris

Dubris was one of the most important forts of the Saxon Shore, as it lay closer to the mainland than any of the other forts. In addition to its eastern location, it also was built on a river estuary. The fort at Dubris functioned as a base for the Roman naval fleet in the Channel, the Classis Britannica. Due to its location, Dubris became the site of a large civilian town, functioning as the main city in cross-Channel trade between Gaul and Britain.

Anderitum

The final Saxon Shore fort mentioned in the Notitia Dignitatum was located on a peninsula when it was first built in the 3rd century. The fort at Anderitum has undergone much reconstruction and use since the Roman occupation, but some of its walls still stand today and show the Roman masonry of the original construction.

Saxon Shore Forts (North to South)
Branodunum (Brancaster)
Gariannonum (Burgh Castle)
Othona (Bradwell-on-Sea)
Regulbium (Reculver)
Rutupiae (Richborough)
Dubris (Dover Castle)
Portus Lemanis (Lympne)
Portus Adurni (Portchester Castle)
Anderitum (Pevensey Castle)
A coin minted during the Carausian occupation of Britain. (circa 288-290 A.D., Londinium)
A coin minted during the Carausian occupation of Britain. (circa 288-290 A.D., Londinium) | Source

Possible Ties to the Carausian Revolt

As if the rising barbarian presence were not enough for Rome to deal with in the 3rd century, Rome also suffered from the presence of a usurper in Britain. Carsusius had at one time been a trusted leader within the Roman military, so trusted that he was given charge of the Classis Britannica. The emperors Maximian and Diocletian charged him with the task of clearing the Channel of its pirate infestation, but Carausius tried to play both sides against the middle.

He was eventually caught and sentenced to death for his role in allowing the pirates free reign of the Channel. He made quite a fortune by taking bribes from the Saxon pirates, and when he learned of the sentence passed in Rome, Carausius opted to secede from the empire rather than give in. With the backing of the Saxon pirates and the legions in Britain and Gaul, Carausius managed to rule the region of Gaul and Britain for a period of 7 years from 286-293 A.D.

Several historians have proposed the theory that the Saxon Shore was bolstered at the bidding of Carausius. Who wouldn't be fearful of the retaliation of Rome if they had pulled a move like Carausius had? Whether true or not, it is interesting to consider the possibility of a Roman fort system built to defend against other Romans.

In reality, it is more likely that the Saxon Shore was built as a defense or control system to help reduce the threat of the barbarian presence in the Channel. The wealthy trade towns situated on the river inlets of southern Britain drew a substantial amount of attention from the barbarian pirates and needed a stout defense. It is possible that several individual forts were commissioned by Carausius, but the bulk of them had earlier foundations, and even if they were used as defensive forts by Carausius, they were probably seized by his forces rather than built by them.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)