biztrac. BETA
COMPANY REGISTER PROFILE
813204622 ORG. NO. 2019 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of tourist offices and destination marketing organisations

TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF

Org. no. 813204622 Norwegian division of foreign business enterprise (NUF) Active
Ownership graph ↗
Revenue 2019 NOK 2.9m
Operating profit NOK 89,000
Equity NOK 194,000

TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF is registered as a norwegian division of foreign business enterprise with organisation number 813204622. The business is classified under activities of tourist offices and destination marketing organisations (NACE 79.901). The most recent filed accounts, for the 2019 financial year, show NOK 2.9m in revenue and NOK 89,000 in operating profit.

Key figures · 2019

Revenue
NOK 2.9m
▲ +34 %
Operating profit
NOK 89,000
▲ +474 %
Equity
NOK 194,000
▲ +56 %
Est. value
NOK 456,000

Financial health · 2019

Liquidity
14.48
Very good
Current assets ÷ current liabilities
Profitability
51.1%
Very good
Return on total assets
Solidity
93.1%
Very good
Equity as a share of total capital

Who owns TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF?

No shareholders are registered for TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF

What is the revenue of TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF?

TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF had revenue of NOK 2.9m in 2019.

Where is TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF based?

TRAVELGROEP NORGE, FILIAL AV NEDERLANDSKE TRAVELGROEP B.V. NUF has its business address in 1017 Ae Amsterdam.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.