BIZTRAC BETA
Development of building projects

KONGSFOSS AS

Org. no. 930635138 Limited company (AS) Lier Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −900
Equity NOK 898
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−900 kr).

KONGSFOSS AS is registered as a limited company in Lier, Buskerud with organisation number 930635138. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bygg- og anleggsarbeider - nybygg, tilbygg, rehabilitering, kjøp og salg av biler, maskiner og utstyr og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −900 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −900
Equity
NOK 898
Est. value
NOK 820

Financial health · 2024

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

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

Who owns KONGSFOSS AS?

LEON JOHANSEN
KONGSFOSS AS
NOK 0 rev. · NOK −900 profit

KONGSFOSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSFOSS AS

Who owns KONGSFOSS AS?

LEON JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of KONGSFOSS AS?

KONGSFOSS AS had revenue of NOK 0 in 2024.

Where is KONGSFOSS AS based?

KONGSFOSS AS has its business address in Gullaug.

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.