Database Rules
Database editing rules
20. General regulations
20.1. This regulation describes the rules for maintaining the database (hereinafter referred to as the DB)
by regional editors, general editors and site administrators. The database contains information collected
by users of the site about vehicles (hereinafter referred to as vehicles) related to the subject of the site.
The site's database is not an official source of information and does not claim to be fully factual,
although it strives for it.
20.2. The database is based on a combination of personal observations, official documents and data
from other online resources. In cases where information from different sources contradicts each other,
information obtained through personal observations is considered the most accurate for inclusion in the
database. The editor has the right to request photographic evidence (of any quality) of personal
observations if they are rather unexpected for a specific city or region.
20.3. The website follows a per-body principle, meaning that the history of the vehicle's body is tracked.
If the body is replaced with a new one, a new profile must be created. If the previous or subsequent
history of the vehicle cannot be traced, this should be noted in the "Vehicle Information" field.
20.4. Renumbering of vehicles is reflected by adding a new sub-profile to the vehicle profile, regardless
of whether the renumbering is officially documented or not. If necessary, the renumbering can be
accompanied by a note in the "Vehicle Information" field, providing official details.
20.4.1. It is strongly discouraged to enter the fleet numbers that are assigned to the vehicle right before
its decommissioning and/or disposal.
20.5. All database fields, including the hidden comment, are subject to section 5 of the general website
rules.
20.6. At the time of publication of the rules, the database is prioritized for currently active vehicles, and
we recommend adding data about them first.
21. Bus depots and their affiliation with cities and regions.
21.1. The website database is divided into cities and regions. When creating a bus depot, the
first step is to determine its actual location. If the actual location of the depot cannot be
determined, the workplace should be used as a reference. In cases where neither the actual
location of the enterprise nor the workplace is known, the legal address or the region of the
vehicle's license plate should be used as a reference.
21.2. For depots with route vehicles located outside the city where they operate, it is
acceptable to create the depot in the city where the workplace is located. For example, a
company operates on routes in the city of Baku, but is based outside of Baku, near the city. This
exception to the rule is well-suited for bus systems that are centralized around a single major
city. The rule is designed to help with photo sorting, ensuring that the city page displays an up-
to-date list of carriers operating on specific city routes, even if the carrier's facility is actually
located outside of that city.
21.3. In cities, sections ("locations") are created for bus companies and their additional
branches. In the event that it is not possible to track the assignment of vehicles to branches,
they should be collected in a single depot. In order to separate branches into a separate
enterprise on the website, it should be possible to track the assignment of vehicles to branches
based on external characteristics of the vehicle, such as the fleet number.
21.4. Regions are divided into sections ("locations") for the regions, and depots are created
within these sections.
21.5. The "Name" field should contain the name of the depot or branch, which is current at
the time of creation or at the time of closure. The "Short name" field should be informative
enough to identify the vehicle, but it should also be as brief as possible. If the company has an
official abbreviation, it is recommended to use it.
21.6. The "Note" field is intended for information about name changes, opening and closing
dates, as well as brief information about the company (address, phone number) and the routes
it serves. Detailed information about the company should be provided on a separate page,
which can also be linked in the "Note" field.
21.6.1. The depot can have one of the following states:
— "Works wand has operating vehicles" — the enterprise is operating and has an active vehicle that is
used for passenger transportation.
— "Works with no operating vehicles" — the enterprise is not liquidated, but does not have an active
vehicle and does not participate in passenger transportation (regardless of the type of operation: route
transportation, charter transportation, etc.).
— "Factory" — the enterprise is a bus vehicle manufacturer, repair facility, manufacturer representative,
or trading platform.
— "Museum" — the enterprise is a bus transport museum.
— "Virtual" — a pseudo depot that is intended to combine and structure individual scattered database
records ("Other").
— "Closed" — the enterprise has been liquidated.
21.7. If a depot covers several regions and has branches in them, then the corresponding sections must
be created in all regions where the depot operates. In these cases, it is necessary to create a group of
depots in order to be able to combine these depots with each other.
21.8. The database is filled in the country's language, in accordance with paragraph 16.3.
22. Vehicle numbers, purpose, dates.
22.1. The main account parameter of a vehicle on the website is the vehicle's license plate.
22.1.1. In cases where a vehicle is operated with a license plate that differs from the
data in the documents, the website reflects the actual situation.
22.2. The license plate applied to the vehicle takes precedence over the number in the
documents if they do not match. Exceptions to this point may only be considered on an
individual basis and with the mandatory condition of uniformity in the city/region
database in this regard. Differences between the actual and documentary numbers may be
noted in the "Vehicle Information" field.
22.2.1. The fleet number left over from the previous owner of the vehicle is not
included in the new vehicle sub-profile.
22.3. There are three types of vehicle purpose:
• Passenger: used for transporting passengers on regular and irregular routes, as well as for
charter and private transportation;
• Service: used for organized transportation of employees of depot using vehicles owned by such
depots;
• Museum: a vehicle preserved for historical purposes. This status should be used even if there is
no actual museum at the depot. It is indicated for all such vehicles and takes precedence over
"Passenger" and "Service." Changing the purpose of a vehicle requires creating a new sub-profile, except
in cases where the purpose was initially incorrect.
22.4. The start date (Valid since...) and end date (Left (or decommissioned)) are specified for
the given combination of enterprise or branch, number, model, and destination. The end date is
optional when the combination of vehicle data changes within one month. For example, if a
vehicle is transferred to another enterprise within a few days, the end date is not required.
22.5. In the event that the date is unknown, for all lines in the profile, except for the
historically first, the start date must still be specified, while selecting the "Do not display"
option. This is necessary for the correct sorting of entries in the profile in chronological order.
22.6. The dates of construction and disposal are specified for a given vehicle body. In the
event that they are known with an accuracy of a day, or with an approximation of several years,
an explanation should be given in the "Vehicle Information" field.
22.7. The date of construction may be updated in the event of vehicle modernization
(including without changing the model, if the body has been reconstructed), the date of disposal
always remains the actual date of the physical termination of the vehicle. It should not be
indicated as a substitute for the date of disposal, if there is no information about the actual
destruction of the vehicle after the disposal.
23. Vehicle states
23.1. Current status — the status of this vehicle subprofile (if this subprofile is not the last one for this
vehicle) or the vehicle itself (if this is the last or only number for this vehicle) at the present time.
Vehicles in the database can have the following statuses:
* In operation — white background — the vehicle is regularly used for its intended purpose (linear
— works with passengers, active service vehicle, running museum exhibit).
* Wasn’t in operation at this depot — green background — a vehicle that has been delivered to the
enterprise for the first time and has not yet been used for its intended purpose at the moment (the
status applies only to the enterprise in which it is displayed, i.e., a used bus may have this status
between the time of purchase and the start of operation at the new enterprise).
* Not in operation — yellow background — the vehicle has not been in operation for a long time (due
to a serious malfunction or organizational reasons). A vehicle from the previous category may be moved
to this category if its return to service has been significantly delayed (more than a year). Also —
nonoperational museum exhibits.
* Withdrawn — red background — the vehicle has been written off in the documents and/or is
physically in a condition from which it cannot be returned to service.
* Decommissioned/awaiting disposal — gray background — the vehicle will no longer be used for its
intended purpose at this enterprise due to its removal from service, which may be related to
preparation for disposal or preparation for sale/transfer.
* Location and status unknown — brown background — Information about the location and
condition of the vehicle is currently unavailable.
* Renumbered/transferred within the city — blue background — the vehicle has been given a new
registration number within the same enterprise and city/region, or has been transferred to another
division in the same city.
* Modernization (model change) — blue background — Vehicles that have undergone
modernization with an official model change.
* Transferred to another city — purple background — the vehicle has been sold or transferred to
another operator in another city/region. This status is assigned if there is accurate information about
the sale or transfer, regardless of the ability to track the status of the vehicle with the new owner.
* Change of license plate within the depot — light blue background — vehicles that have changed
their license plate within the same depot.
23.2. If the change in status occurred as a result of a certain event (accident, fire, repair, etc.),
this can be noted in brief in the "Vehicle Information" field.
23.3. If it is not possible to monitor the condition of the vehicle on a regular basis, we
recommend not using the "Not in operation" status in all cases, except for serious accidents and
widely known mass cases of removal from use of this model of vehicle at the enterprise.
24. Vehicle model and factory data
24.1. The vehicle model and chassis model (if there is a chassis) should be specified as fully as possible. If
the vehicle model is unknown, select "model unknown" from the list.
24.2. If there is no known vehicle model in the database, select the model "other models." In this case,
the actual vehicle model should be specified in the note. If there is no known chassis model in the
database, leave the "Chassis" field blank and specify the chassis name in the note.
24.3. The final VIN of the vehicle is indicated in the "VIN" field. If the vehicle consists of a body and a
chassis, the VIN of the body is indicated. If it is not used, the field remains blank.
24.3.1. If the documents and body do not match, the "VIN" field must be left blank.
24.4. The chassis number or VIN is entered in the "Chassis No." field. If the chassis VIN and final VIN
match, the field is left blank.
24.5. The "Factory No. " field indicates the serial factory number of the vehicle. Depending on the
vehicle model, this may be either the last few characters of the final VIN or a separate number.
24.6. The year (mandatory, if known) and month (optional) of the actual construction of the vehicle
body are entered in the "Built" field.
24.7. The "Scrapped" field indicates the year and month (if known) of the actual scrapping of the vehicle
body.
24.8. The parent model of the vehicle is determined by the body, not by the commercial name of several
models.
25. Notes and information about the vehicle
25.1. The "Note" field is used to indicate information related to a specific subprofile:
• the name of the operator, if the vehicle is in a pseudo-enterprise;
• the name of the branch of the enterprise to which the vehicle is assigned.
25.2. The "Vehicle information" field provides, among other things, the following purposes:
• providing additional information related to the vehicle as a whole, as well as notes related to several
numbers/purposes at the same time;
• clarification of data entered in other fields;
• links to photos on external resources and other additional information;
• links to data sources, if any were used.
It is recommended that this field be kept in chronological order.
20. General regulations
20.1. This regulation describes the rules for maintaining the database (hereinafter referred to as the DB)
by regional editors, general editors and site administrators. The database contains information collected
by users of the site about vehicles (hereinafter referred to as vehicles) related to the subject of the site.
The site's database is not an official source of information and does not claim to be fully factual,
although it strives for it.
20.2. The database is based on a combination of personal observations, official documents and data
from other online resources. In cases where information from different sources contradicts each other,
information obtained through personal observations is considered the most accurate for inclusion in the
database. The editor has the right to request photographic evidence (of any quality) of personal
observations if they are rather unexpected for a specific city or region.
20.3. The website follows a per-body principle, meaning that the history of the vehicle's body is tracked.
If the body is replaced with a new one, a new profile must be created. If the previous or subsequent
history of the vehicle cannot be traced, this should be noted in the "Vehicle Information" field.
20.4. Renumbering of vehicles is reflected by adding a new sub-profile to the vehicle profile, regardless
of whether the renumbering is officially documented or not. If necessary, the renumbering can be
accompanied by a note in the "Vehicle Information" field, providing official details.
20.4.1. It is strongly discouraged to enter the fleet numbers that are assigned to the vehicle right before
its decommissioning and/or disposal.
20.5. All database fields, including the hidden comment, are subject to section 5 of the general website
rules.
20.6. At the time of publication of the rules, the database is prioritized for currently active vehicles, and
we recommend adding data about them first.
21. Bus depots and their affiliation with cities and regions.
21.1. The website database is divided into cities and regions. When creating a bus depot, the
first step is to determine its actual location. If the actual location of the depot cannot be
determined, the workplace should be used as a reference. In cases where neither the actual
location of the enterprise nor the workplace is known, the legal address or the region of the
vehicle's license plate should be used as a reference.
21.2. For depots with route vehicles located outside the city where they operate, it is
acceptable to create the depot in the city where the workplace is located. For example, a
company operates on routes in the city of Baku, but is based outside of Baku, near the city. This
exception to the rule is well-suited for bus systems that are centralized around a single major
city. The rule is designed to help with photo sorting, ensuring that the city page displays an up-
to-date list of carriers operating on specific city routes, even if the carrier's facility is actually
located outside of that city.
21.3. In cities, sections ("locations") are created for bus companies and their additional
branches. In the event that it is not possible to track the assignment of vehicles to branches,
they should be collected in a single depot. In order to separate branches into a separate
enterprise on the website, it should be possible to track the assignment of vehicles to branches
based on external characteristics of the vehicle, such as the fleet number.
21.4. Regions are divided into sections ("locations") for the regions, and depots are created
within these sections.
21.5. The "Name" field should contain the name of the depot or branch, which is current at
the time of creation or at the time of closure. The "Short name" field should be informative
enough to identify the vehicle, but it should also be as brief as possible. If the company has an
official abbreviation, it is recommended to use it.
21.6. The "Note" field is intended for information about name changes, opening and closing
dates, as well as brief information about the company (address, phone number) and the routes
it serves. Detailed information about the company should be provided on a separate page,
which can also be linked in the "Note" field.
21.6.1. The depot can have one of the following states:
— "Works wand has operating vehicles" — the enterprise is operating and has an active vehicle that is
used for passenger transportation.
— "Works with no operating vehicles" — the enterprise is not liquidated, but does not have an active
vehicle and does not participate in passenger transportation (regardless of the type of operation: route
transportation, charter transportation, etc.).
— "Factory" — the enterprise is a bus vehicle manufacturer, repair facility, manufacturer representative,
or trading platform.
— "Museum" — the enterprise is a bus transport museum.
— "Virtual" — a pseudo depot that is intended to combine and structure individual scattered database
records ("Other").
— "Closed" — the enterprise has been liquidated.
21.7. If a depot covers several regions and has branches in them, then the corresponding sections must
be created in all regions where the depot operates. In these cases, it is necessary to create a group of
depots in order to be able to combine these depots with each other.
21.8. The database is filled in the country's language, in accordance with paragraph 16.3.
22. Vehicle numbers, purpose, dates.
22.1. The main account parameter of a vehicle on the website is the vehicle's license plate.
22.1.1. In cases where a vehicle is operated with a license plate that differs from the
data in the documents, the website reflects the actual situation.
22.2. The license plate applied to the vehicle takes precedence over the number in the
documents if they do not match. Exceptions to this point may only be considered on an
individual basis and with the mandatory condition of uniformity in the city/region
database in this regard. Differences between the actual and documentary numbers may be
noted in the "Vehicle Information" field.
22.2.1. The fleet number left over from the previous owner of the vehicle is not
included in the new vehicle sub-profile.
22.3. There are three types of vehicle purpose:
• Passenger: used for transporting passengers on regular and irregular routes, as well as for
charter and private transportation;
• Service: used for organized transportation of employees of depot using vehicles owned by such
depots;
• Museum: a vehicle preserved for historical purposes. This status should be used even if there is
no actual museum at the depot. It is indicated for all such vehicles and takes precedence over
"Passenger" and "Service." Changing the purpose of a vehicle requires creating a new sub-profile, except
in cases where the purpose was initially incorrect.
22.4. The start date (Valid since...) and end date (Left (or decommissioned)) are specified for
the given combination of enterprise or branch, number, model, and destination. The end date is
optional when the combination of vehicle data changes within one month. For example, if a
vehicle is transferred to another enterprise within a few days, the end date is not required.
22.5. In the event that the date is unknown, for all lines in the profile, except for the
historically first, the start date must still be specified, while selecting the "Do not display"
option. This is necessary for the correct sorting of entries in the profile in chronological order.
22.6. The dates of construction and disposal are specified for a given vehicle body. In the
event that they are known with an accuracy of a day, or with an approximation of several years,
an explanation should be given in the "Vehicle Information" field.
22.7. The date of construction may be updated in the event of vehicle modernization
(including without changing the model, if the body has been reconstructed), the date of disposal
always remains the actual date of the physical termination of the vehicle. It should not be
indicated as a substitute for the date of disposal, if there is no information about the actual
destruction of the vehicle after the disposal.
23. Vehicle states
23.1. Current status — the status of this vehicle subprofile (if this subprofile is not the last one for this
vehicle) or the vehicle itself (if this is the last or only number for this vehicle) at the present time.
Vehicles in the database can have the following statuses:
* In operation — white background — the vehicle is regularly used for its intended purpose (linear
— works with passengers, active service vehicle, running museum exhibit).
* Wasn’t in operation at this depot — green background — a vehicle that has been delivered to the
enterprise for the first time and has not yet been used for its intended purpose at the moment (the
status applies only to the enterprise in which it is displayed, i.e., a used bus may have this status
between the time of purchase and the start of operation at the new enterprise).
* Not in operation — yellow background — the vehicle has not been in operation for a long time (due
to a serious malfunction or organizational reasons). A vehicle from the previous category may be moved
to this category if its return to service has been significantly delayed (more than a year). Also —
nonoperational museum exhibits.
* Withdrawn — red background — the vehicle has been written off in the documents and/or is
physically in a condition from which it cannot be returned to service.
* Decommissioned/awaiting disposal — gray background — the vehicle will no longer be used for its
intended purpose at this enterprise due to its removal from service, which may be related to
preparation for disposal or preparation for sale/transfer.
* Location and status unknown — brown background — Information about the location and
condition of the vehicle is currently unavailable.
* Renumbered/transferred within the city — blue background — the vehicle has been given a new
registration number within the same enterprise and city/region, or has been transferred to another
division in the same city.
* Modernization (model change) — blue background — Vehicles that have undergone
modernization with an official model change.
* Transferred to another city — purple background — the vehicle has been sold or transferred to
another operator in another city/region. This status is assigned if there is accurate information about
the sale or transfer, regardless of the ability to track the status of the vehicle with the new owner.
* Change of license plate within the depot — light blue background — vehicles that have changed
their license plate within the same depot.
23.2. If the change in status occurred as a result of a certain event (accident, fire, repair, etc.),
this can be noted in brief in the "Vehicle Information" field.
23.3. If it is not possible to monitor the condition of the vehicle on a regular basis, we
recommend not using the "Not in operation" status in all cases, except for serious accidents and
widely known mass cases of removal from use of this model of vehicle at the enterprise.
24. Vehicle model and factory data
24.1. The vehicle model and chassis model (if there is a chassis) should be specified as fully as possible. If
the vehicle model is unknown, select "model unknown" from the list.
24.2. If there is no known vehicle model in the database, select the model "other models." In this case,
the actual vehicle model should be specified in the note. If there is no known chassis model in the
database, leave the "Chassis" field blank and specify the chassis name in the note.
24.3. The final VIN of the vehicle is indicated in the "VIN" field. If the vehicle consists of a body and a
chassis, the VIN of the body is indicated. If it is not used, the field remains blank.
24.3.1. If the documents and body do not match, the "VIN" field must be left blank.
24.4. The chassis number or VIN is entered in the "Chassis No." field. If the chassis VIN and final VIN
match, the field is left blank.
24.5. The "Factory No. " field indicates the serial factory number of the vehicle. Depending on the
vehicle model, this may be either the last few characters of the final VIN or a separate number.
24.6. The year (mandatory, if known) and month (optional) of the actual construction of the vehicle
body are entered in the "Built" field.
24.7. The "Scrapped" field indicates the year and month (if known) of the actual scrapping of the vehicle
body.
24.8. The parent model of the vehicle is determined by the body, not by the commercial name of several
models.
25. Notes and information about the vehicle
25.1. The "Note" field is used to indicate information related to a specific subprofile:
• the name of the operator, if the vehicle is in a pseudo-enterprise;
• the name of the branch of the enterprise to which the vehicle is assigned.
25.2. The "Vehicle information" field provides, among other things, the following purposes:
• providing additional information related to the vehicle as a whole, as well as notes related to several
numbers/purposes at the same time;
• clarification of data entered in other fields;
• links to photos on external resources and other additional information;
• links to data sources, if any were used.
It is recommended that this field be kept in chronological order.
Dark Theme
© BusCloud administration and authors of photos, 2026
Using any images from this website without authors' permission is prohibited.
Using any images from this website without authors' permission is prohibited.