BIZTRAC BETA
Rental and operating of own or leased real estate

KVÆRNERFOSSEN AS

Org. no. 934779509 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 50,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-16 Aksjekapital registrert 2026-04-16.

KVÆRNERFOSSEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934779509. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av egen fast eiendom og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns KVÆRNERFOSSEN AS?

BLÅIN AS
KVÆRNERFOSSEN AS
NOK 0 rev. · NOK 0 profit

KVÆRNERFOSSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVÆRNERFOSSEN AS

Who owns KVÆRNERFOSSEN AS?

BLÅIN AS is the largest registered owner, with 100.0%.

What is the revenue of KVÆRNERFOSSEN AS?

KVÆRNERFOSSEN AS had revenue of NOK 0 in 2024.

Where is KVÆRNERFOSSEN AS based?

KVÆRNERFOSSEN AS has its business address in Trondheim.

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.