Djibouti vs Hong Kong SAR, China

Djibouti vs Hong Kong SAR, China, head to head across 5 shared rankings. Djibouti ranks higher in 0, Hong Kong SAR, China ranks higher in 5. On that count Hong Kong SAR, China comes out ahead overall, though each ranking measures something different, so the detail below matters more than the tally.

Ranking by ranking: in Most trade-dependent economies (trade as share of GDP), Djibouti is #7 with 206.3 % of GDP and Hong Kong SAR, China is #1 with 396.65 % of GDP (Hong Kong SAR, China ahead by 6); in Countries with the highest goods trade as a share of GDP, Djibouti is #2 with 267.14 % of GDP and Hong Kong SAR, China is #1 with 371.02 % of GDP (Hong Kong SAR, China ahead by 1); in Countries where the most urban people live in the largest city, Djibouti is #8 with 71.33 % of urban population and Hong Kong SAR, China is #1 with 100 % of urban population (Hong Kong SAR, China ahead by 7); in Countries by net primary income, Djibouti is #36 with 115.93 BoP, current US$ million and Hong Kong SAR, China is #4 with 42.9k BoP, current US$ million (Hong Kong SAR, China ahead by 32); in Countries by trade in services, Djibouti is #39 with 45.82 % of GDP and Hong Kong SAR, China is #32 with 48.83 % of GDP (Hong Kong SAR, China ahead by 7).

Within each ranking both entries are measured by the same metric from the same source at the same time, which makes every row a like-for-like comparison. Across rankings the metrics differ, so a lead in one does not cancel out a deficit in another. The rank history chart tracks both entries through every published snapshot of the first shared ranking.

Dates shown next to each ranking are the capture dates of the snapshots used, so you always know how current a comparison is. Each entry also has a profile page listing every ranking it appears in, and each ranking has a quiz if you want to test whether you could have named the top 10.

Top10Earth never estimates or edits a value: each number is fetched from its source, hashed, stored and ranked by software, then checked by a quality gate before it is published. If a refresh fails the gate, the previous snapshot stays live and the problem is reviewed by a person.