BIZTRAC BETA
Rental and operating of own or leased real estate

KRAGERØ INDUSTRIBYGGUTLEIE AS

Org. no. 922216061 Limited company (AS) Kragerø Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 703,000
Equity NOK 1.4m
Incorporated 2019
Share capital NOK 1.7m

KRAGERØ INDUSTRIBYGGUTLEIE AS is registered as a limited company in Kragerø, Telemark with organisation number 922216061. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.7m, divided into 1800 shares. The company's stated purpose is: “Utleie av fast eiendom samt investeringer i andre relaterte virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 703,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 703,000
Equity
NOK 1.4m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
2.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.2%
Good
Equity as a share of total capital

Who owns KRAGERØ INDUSTRIBYGGUTLEIE AS?

PAUL ÅGE HANSEN
KRAGERØ INDUSTRIBYGGUTLEIE AS
NOK 1.3m rev. · NOK 703,000 profit

KRAGERØ INDUSTRIBYGGUTLEIE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRAGERØ INDUSTRIBYGGUTLEIE AS

Who owns KRAGERØ INDUSTRIBYGGUTLEIE AS?

PAUL ÅGE HANSEN is the largest registered owner, with 33.3%.

What is the revenue of KRAGERØ INDUSTRIBYGGUTLEIE AS?

KRAGERØ INDUSTRIBYGGUTLEIE AS had revenue of NOK 1.3m in 2025.

Who is the general manager of KRAGERØ INDUSTRIBYGGUTLEIE AS?

Nina Wessel Toft is registered as general manager of KRAGERØ INDUSTRIBYGGUTLEIE AS.

Where is KRAGERØ INDUSTRIBYGGUTLEIE AS based?

KRAGERØ INDUSTRIBYGGUTLEIE AS has its business address in Sannidal.

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.