BIZTRAC BETA
Civil engineering activities

SIV ING ERLING F JOHNSEN AS

Org. no. 946686344 Limited company (AS) Oslo Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 2.8m
Equity NOK 245,000
Incorporated 1988
Share capital NOK 100,000

SIV ING ERLING F JOHNSEN AS is registered as a limited company in Oslo, Oslo with organisation number 946686344. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet og entreprenørvirksomhet og dertil hørende virksomhet,herunder å eie aksjer og/eller andeler i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 2.8m
Equity
NOK 245,000
Est. value
NOK 8.4m

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.4%
Weak
Equity as a share of total capital

Who owns SIV ING ERLING F JOHNSEN AS?

ERLING FRIDVOLD JOHNSEN
SIV ING ERLING F JOHNSEN AS
NOK 7.6m rev. · NOK 2.8m profit

SIV ING ERLING F JOHNSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIV ING ERLING F JOHNSEN AS

Who owns SIV ING ERLING F JOHNSEN AS?

ERLING FRIDVOLD JOHNSEN is the largest registered owner, with 70.0%.

What is the revenue of SIV ING ERLING F JOHNSEN AS?

SIV ING ERLING F JOHNSEN AS had revenue of NOK 7.6m in 2024.

Who is the general manager of SIV ING ERLING F JOHNSEN AS?

Erling Fridvold Johnsen is registered as general manager of SIV ING ERLING F JOHNSEN AS.

Where is SIV ING ERLING F JOHNSEN AS based?

SIV ING ERLING F JOHNSEN AS has its business address in Oslo.

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.