Work in progress. People, families and relationships are auto-extracted and unverified.

Ashford

County: Kent. 8 entries. Search all entries for this place →

Coordinates: matched against the Ordnance Survey gazetteer. Provenance is recorded for every geocode; coordinates are an aid, verify before relying on them.

Spellings in the source

Possibly the same place (suggestions, not merged)

Similarly-spelled place-names (e.g. Notingham → Nottingham). Kept separate until a human confirms.

Request a place merge

Where the court travelled (to and from Ashford)

Arrived from

Departed to

A “move” links two consecutive dated entries whose places differ and fall within 60 days of each other — a coarse proxy for the great seal's journeys, not an itinerary of every step. Distances are straight-line, so real road journeys were longer.

Explore Ashford in the location network → see it on the map →

Summary

5Documents
0Discrete acts
7People named
1290-10-09 – 1315-06-13Date range

Over time

Acts by type

People most often named here

By roll

  • Fine Rolls 3
  • Close Rolls 1
  • Patent Rolls 1

Entries

  1. 1290-10-09 date: inferred

    Richard de Acovere, John Elis of Langesdon, and William Folejaumbe of Gratton acknowledge that they owe to William de Hamelton q 191. 16s. 103d.; to be levied, in default of payment, of their lands and , chattels in cos.…

  2. 1302-09-19 date: inferred

    Order to the same to make partition of the lands late of John de Danethorp, tenant in chief as of the honour of Albemarle, in the king's hand, into two equal parts, and to deliver to John, nephew and one of the heirs of …

  3. 1310-06-13 date: inferred

    with clause, until Michaelmas, for Walter de Gras, going on service beyond the seas. By p's.…

  4. 1315-06-13 date: inferred

    Order to the escheator on this side Trent to deliver to Robert son and heir of Thomas Tuchet, tenant in chief, the lands of his said father, he having done homage. By p.s.…

  5. 1315-06-13 date: inferred

    The like to the escheator beyond Trent.…

Report a problem

Spotted an error — a wrong date or place, a misread text, people wrongly combined or split? Reports keep the corpus trustworthy.