biztrac. BETA
COMPANY REGISTER PROFILE
924523360 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of excursion and event organisers

BRUNLANES UNDERHOLDNING AS

Org. no. 924523360 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 936,000
Operating profit NOK 135,000
Equity NOK 586,000
Incorporated 2020
Share capital NOK 30,000

BRUNLANES UNDERHOLDNING AS is registered as a limited company in Larvik, Vestfold with organisation number 924523360. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Underholdning- og festivalvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 936,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 936,000
▲ +7 %
Operating profit
NOK 135,000
▼ −44 %
Equity
NOK 586,000
▲ +17 %
Est. value
NOK 922,000

Financial health · 2025

Liquidity
9.93
Very good
Current assets ÷ current liabilities
Profitability
24.6%
Very good
Return on total assets
Solidity
89.9%
Very good
Equity as a share of total capital

Who owns BRUNLANES UNDERHOLDNING AS?

BRUNLANES UNDERHOLDNING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRUNLANES UNDERHOLDNING AS

Who owns BRUNLANES UNDERHOLDNING AS?

Tom Roger Wisting is the largest registered owner, with 30.5%.

What is the revenue of BRUNLANES UNDERHOLDNING AS?

BRUNLANES UNDERHOLDNING AS had revenue of NOK 936,000 in 2025.

Who is the general manager of BRUNLANES UNDERHOLDNING AS?

Tom Roger Wisting is registered as general manager of BRUNLANES UNDERHOLDNING AS.

Where is BRUNLANES UNDERHOLDNING AS based?

BRUNLANES UNDERHOLDNING AS has its business address in Nevlunghavn.

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.