BIZTRAC BETA
Activities of excursion and event organisers

COMPLETE TRAVELS AS

Org. no. 921076770 Limited company (AS) Færder Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 404,000
Operating profit NOK 53,000
Equity NOK 41,000
Incorporated 2018
Share capital NOK 30,000

COMPLETE TRAVELS AS is registered as a limited company in Færder, Vestfold with organisation number 921076770. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Arrangør av reiser i inn- og utland. Kursing, events, sportsarrangementer samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 404,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 404,000
Operating profit
NOK 53,000
Equity
NOK 41,000
Est. value
NOK 238,000

Financial health · 2025

Liquidity
4.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
75.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns COMPLETE TRAVELS AS?

RONJA HAVELIN BUER
COMPLETE TRAVELS AS
NOK 404,000 rev. · NOK 53,000 profit

COMPLETE TRAVELS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COMPLETE TRAVELS AS

Who owns COMPLETE TRAVELS AS?

RONJA HAVELIN BUER is the largest registered owner, with 100.0%.

What is the revenue of COMPLETE TRAVELS AS?

COMPLETE TRAVELS AS had revenue of NOK 404,000 in 2025.

Who is the general manager of COMPLETE TRAVELS AS?

Ronja Havelin Buer is registered as general manager of COMPLETE TRAVELS AS.

Where is COMPLETE TRAVELS AS based?

COMPLETE TRAVELS AS has its business address in Husøysund.

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

Report a problem

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