biztrac. BETA
COMPANY REGISTER PROFILE
989242261 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Camping grounds and recreational vehicle parks

WOLLERT-NIELSEN INVEST AS

Org. no. 989242261 Limited company (AS) Tønsberg Incorporated 2005 Active
Operating profit NOK −36,000
Equity NOK 5.4m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−36k kr).

WOLLERT-NIELSEN INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 989242261. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å eie andeler i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −36,000
▼ −61 %
Equity
NOK 5.4m
▲ +77 %
Est. value
NOK 30.9m

Financial health · 2025

Liquidity
6.38
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
84.5%
Very good
Equity as a share of total capital

Who owns WOLLERT-NIELSEN INVEST AS?

WOLLERT-NIELSEN INVEST AS
· NOK −36,000 profit

WOLLERT-NIELSEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WOLLERT-NIELSEN INVEST AS own?

WOLLERT-NIELSEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WOLLERT-NIELSEN INVEST AS

Who owns WOLLERT-NIELSEN INVEST AS?

Maria Wollert-Nielsen is the largest registered owner, with 50.0%.

Who is the general manager of WOLLERT-NIELSEN INVEST AS?

Svein Wollert-Nielsen is registered as general manager of WOLLERT-NIELSEN INVEST AS.

Where is WOLLERT-NIELSEN INVEST AS based?

WOLLERT-NIELSEN INVEST AS has its business address in Tolvsrød.

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.