BIZTRAC BETA
Construction of residential and non-residential buildings

KRANSALAGET AS

Org. no. 995606569 Limited company (AS) Kvam Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 339,000
Equity NOK −59,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−59k kr).

KRANSALAGET AS is registered as a limited company in Kvam, Vestland with organisation number 995606569. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygninger og konstruksjoner. Kjøp, salg og utleie av fast eiendom etc.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 339,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 339,000
Equity
NOK −59,000
Est. value
NOK 2.3m

Financial health · 2025

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

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

Who owns KRANSALAGET AS?

LARS MÅGE
KRANSALAGET AS
NOK 4.7m rev. · NOK 339,000 profit

KRANSALAGET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRANSALAGET AS

Who owns KRANSALAGET AS?

LARS MÅGE is the largest registered owner, with 100.0%.

What is the revenue of KRANSALAGET AS?

KRANSALAGET AS had revenue of NOK 4.7m in 2025.

Who is the general manager of KRANSALAGET AS?

Lars Måge is registered as general manager of KRANSALAGET AS.

Where is KRANSALAGET AS based?

KRANSALAGET AS has its business address in Strandebarm.

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.