Government agencies communicate via .gov.sg websites (e.g. go.gov.sg/open). Trusted websites
Secure websites use HTTPS
Look for a lock () or https:// as an added precaution. Share sensitive information only on official, secure websites.
Real-time APIs will be unavailable from September 19th, 2024, 06:00 pm to September 19th, 2024, 10:00 pm due to upstream service's system maintenance. We apologise for the inconvenience caused.
AnnualTourismReceiptsbyMajorComponents.csv (16 rows, 497 B)
Year
Datetime (Year) "YYYY"
Major Components
Text (General)
Tourism Receipts (TR)
Numeric (General)
Tourism Receipts Per Capita (TRPCE)
Numeric (General)
(Null)0.0%
(Null)0.0%
(Null)0.0%
(Null)0.0%
2013
All Components
23469
1508
2013
Accommodation
5332
343
2013
Food & Beverage
2294
147
2013
Shopping
4553
292
2013
Sightseeing, Entertainment & Gaming
5471
351
2013
Local Transport
835
54
2013
Medical
832
53
2013
Others
4152
267
2014
All Components
23560
1561
2014
Accommodation
5309
352
No results found
Column legend
Title
Column name
Data type
Unit of measure
Description
Year
period
Datetime (Year) "YYYY"
-
-
Major Components
components
Text (General)
-
TR Components: (1) Accommodation (2) Food & Beverage (3) Shopping (4) Sightseeing, Entertainment & Gaming (5) Local Transport (6) Medical (7) Other. Other TR components include expenditure on airfares, port taxes, business, education and transit visitors.
Tourism Receipts (TR)
tot_tr
Numeric (General)
S$ million
Tourism Receipts comprise any expenditure incurred by visitors (including transit passengers, foreign air/sea crew and foreign students) during their stay in Singapore as well as the amount they prepaid on components such as accommodation and sightseeing tours before arrival.
Tourism Receipts Per Capita (TRPCE)
trpce
Numeric (General)
S$
Per capita expenditure refers to per person per trip expenditure.
Sample OpenAPI query
This code can be used to test a sample API query. It retrieves the data catalogue of this dataset. For a complete guide on query parameters and syntax, please refer to the API documentation. Try it out on your browser to see the response schema.