database check

Part One involves checking a selection of random hex codes against your database to see how up to date your info is. On the chart below, starting from the right hand column, check the hex codes in your database, the registration you should have is in the green column, if it's not, the further left you have to work to match what is in your database will show how far out of date that entry is, via the date in the de-registered column and/or how many times that frame has been re-registered before you match your database entry.

The UK follows the practice of keeping the hex code with the frame, as demonstrated above. Section Two demonstrates how in countries that have a system where the hex code is permanently tied to the registration
(Canada, Australia, Denmark, Finland, France, Germany, Greece, Portugal, Romania, Russia, South Africa, Turkey, Switzerland, USA(civil), and Yugoslavia) there can be multiple frames with the same registration/hex
code combination used. On the chart below, check the hex code at the top of each column (in yellow) and the current info (in green) against your database, or work down until a match is made, again, the de-registered date showing how out of date your database is.

These are but a few examples of how badly out of date your database can become without you knowing. Possibly only one bit of info might change, such as the construction number for a new / replacement frame, but could go undetected as the registration and hex wouldn't change. dbpop will alert you through the 'new' logo / flag feature, as well as RePop updating all the relevant info