BIZTRAC BETA
Site preparation

JAN PETTER OLSEN AS

Org. no. 814187012 Limited company (AS) Nesodden Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 61,000
Equity NOK −1.4m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).

JAN PETTER OLSEN AS is registered as a limited company in Nesodden, Akershus with organisation number 814187012. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenørdrift, transportvirksomhet og annen virksomhet som faller naturlig sammen med dette samt investering i andre selskaper ved aksjeinnehav eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 61,000
Equity
NOK −1.4m
Est. value
NOK 409,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1158.1%
Weak
Equity as a share of total capital

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

Who owns JAN PETTER OLSEN AS?

JAN PETTER OLSEN
JAN PETTER OLSEN AS
NOK 2.8m rev. · NOK 61,000 profit

JAN PETTER OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAN PETTER OLSEN AS

Who owns JAN PETTER OLSEN AS?

JAN PETTER OLSEN is the largest registered owner, with 100.0%.

What is the revenue of JAN PETTER OLSEN AS?

JAN PETTER OLSEN AS had revenue of NOK 2.8m in 2024.

Where is JAN PETTER OLSEN AS based?

JAN PETTER OLSEN AS has its business address in Nesoddtangen.

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.