Boat Data

How to Read a Boatpedia Model Page

A Boatpedia model page separates identity, specifications, source evidence, market observations, visual assets, and inspection notes.

Level
foundation
Read time
7 min
Sources
1

Read the Page in This Order

  1. 1

    Confirm the identity

    Start with builder, model name, aliases, production years, and variant labels. Many boat names are reused across generations or markets.

  2. 2

    Check the core dimensions

    LOA, beam, draft, displacement, and air draft define the basic operating envelope. Treat missing or variant-dependent fields as unresolved data, not zero values.

  3. 3

    Review the source status

    Official builder pages, brochures, manuals, class associations, and verified documents carry more weight than broker listings or owner reports.

  4. 4

    Separate market from facts

    Market cards describe observed listings and asking prices. They do not replace a survey, appraisal, sea trial, or transaction history.

  5. 5

    Use inspection prompts as prompts

    Inspection notes are questions to verify during viewing, survey, or ownership handover. They are not proof that every hull has the issue.

Core Page Fields

FieldMeaningBoatpedia use
Model identityBuilder, model, variant, aliases, and production band.Helps connect the page to search results, market listings, and related models.Renamed models and regional names may need aliases before search feels complete.
SpecificationsMeasured or source-published values such as LOA, beam, draft, displacement, sail area, tankage, and power.Feeds comparison, filters, print views, and ratio calculations.Some fields vary by keel, rig, layout, engine package, or model year.
Source documentsOfficial pages, brochures, manuals, class records, reviews, and verified attachments.Explains where facts came from and when they were last verified.
Market trackingObserved sale-listing data such as active listings, asking price, status, source, and first/last seen dates.Shows market activity and price-history context.Asking price is not the same as sold price or fair value.

Model Page Trust Cues

A model page should make the source, freshness, and caveat for each important claim easy to see.
Source document
Official or reviewed evidence that supports a model fact.
Model fact
The displayed value and whether it belongs to the base model or a variant.
User caveat
The visible note that explains confidence, freshness, units, or uncertainty.

Before Trusting a Field

Specification check

  • Is the source official, class-backed, or otherwise high-trust?
  • Does the value belong to the base model or a specific variant?
  • Does the value include original units and normalized units?

Market check

  • Is the module labeled as asking-price data?
  • Is sample size visible?
  • Is latest observation date visible?
References

Sources and Method Notes

Boatpedia reference

Boatpedia reference standards

Public guidance for reading model facts, source notes, market context, and data caveats on Boatpedia.

Open source