biztrac. BETA
COMPANY REGISTER PROFILE
920399576 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KONGHOLM BOLIGUTLEIE AS

Org. no. 920399576 Limited company (AS) Bamble Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 13.8m
Operating profit NOK 10.8m
Equity NOK 21.9m
Incorporated 2018
Share capital NOK 30,000

KONGHOLM BOLIGUTLEIE AS is registered as a limited company in Bamble, Telemark with organisation number 920399576. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.8m in revenue and NOK 10.8m in operating profit.

Former names: SMEDGATEN 22 HOLDING AS, KONGHOLM AS

Key figures · 2025

Revenue
NOK 13.8m
▲ +0 %
Operating profit
NOK 10.8m
▲ +0 %
Equity
NOK 21.9m
▲ +0 %
Est. value
NOK 33.7m

Financial health · 2025

Liquidity
29.39
Very good
Current assets ÷ current liabilities
Profitability
23.7%
Very good
Return on total assets
Solidity
54.5%
Very good
Equity as a share of total capital

Who owns KONGHOLM BOLIGUTLEIE AS?

ITERATIV EIENDOM AS NO
KONGHOLM BOLIGUTLEIE AS
NOK 13.8m rev. · NOK 10.8m profit

KONGHOLM BOLIGUTLEIE AS has 1 registered shareholder:

  • ITERATIV EIENDOM AS 100.0%
All shareholders and roles →

Frequently asked questions about KONGHOLM BOLIGUTLEIE AS

Who owns KONGHOLM BOLIGUTLEIE AS?

ITERATIV EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KONGHOLM BOLIGUTLEIE AS?

KONGHOLM BOLIGUTLEIE AS had revenue of NOK 13.8m in 2025.

Where is KONGHOLM BOLIGUTLEIE AS based?

KONGHOLM BOLIGUTLEIE AS has its business address in Stathelle.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.