BIZTRAC BETA
Site preparation

ASBJØRN SIMENSEN. AS

Org. no. 990015996 Limited company (AS) Alta Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 12.6m
Operating profit NOK 799,000
Equity NOK 1.1m
Incorporated 2006
Employees 5
Share capital NOK 400,000

ASBJØRN SIMENSEN. AS is registered as a limited company in Alta, Finnmark with organisation number 990015996. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Eie og drift av anleggsmaskiner, arbeid på tomter, vann og kloakk, vedproduksjon, samt annen virksomhet som måtte falle naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.6m in revenue and NOK 799,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.6m
Operating profit
NOK 799,000
Equity
NOK 1.1m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.9%
Satisfactory
Equity as a share of total capital

Who owns ASBJØRN SIMENSEN. AS?

ODDGEIR HÅGENSEN SIMENSEN
ASBJØRN SIMENSEN. AS
NOK 12.6m rev. · NOK 799,000 profit

ASBJØRN SIMENSEN. AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ASBJØRN SIMENSEN. AS

Who owns ASBJØRN SIMENSEN. AS?

ODDGEIR HÅGENSEN SIMENSEN is the largest registered owner, with 50.0%.

What is the revenue of ASBJØRN SIMENSEN. AS?

ASBJØRN SIMENSEN. AS had revenue of NOK 12.6m in 2024.

Who is the general manager of ASBJØRN SIMENSEN. AS?

Oddgeir Hågensen Simensen is registered as general manager of ASBJØRN SIMENSEN. AS.

Where is ASBJØRN SIMENSEN. AS based?

ASBJØRN SIMENSEN. AS has its business address in Alta.

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.