BIZTRAC BETA
Rental and operating of own or leased real estate

KJØPMANNSBRÅTET EIENDOM AS

Org. no. 990687838 Limited company (AS) Haugesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 2.8m
Equity NOK 14.0m
Incorporated 2006
Share capital NOK 11.9m

KJØPMANNSBRÅTET EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 990687838. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 11.9m, divided into 1322223 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 2.8m
Equity
NOK 14.0m
Est. value
NOK 14.4m

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns KJØPMANNSBRÅTET EIENDOM AS?

TRI PLUSS AS
KJØPMANNSBRÅTET EIENDOM AS
NOK 3.9m rev. · NOK 2.8m profit

KJØPMANNSBRÅTET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJØPMANNSBRÅTET EIENDOM AS own?

KJØPMANNSBRÅTET EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KJØPMANNSBRÅTET EIENDOM AS

Who owns KJØPMANNSBRÅTET EIENDOM AS?

TRI PLUSS AS is the largest registered owner, with 100.0%.

What is the revenue of KJØPMANNSBRÅTET EIENDOM AS?

KJØPMANNSBRÅTET EIENDOM AS had revenue of NOK 3.9m in 2025.

Where is KJØPMANNSBRÅTET EIENDOM AS based?

KJØPMANNSBRÅTET EIENDOM AS has its business address in Haugesund.

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.