BIZTRAC BETA
Construction of residential and non-residential buildings

KRUSEMARKA EIENDOM AS

Org. no. 920956270 Limited company (AS) Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 708,000
Operating profit NOK 409,000
Equity NOK 907,000
Incorporated 2018
Share capital NOK 500,000

KRUSEMARKA EIENDOM AS is registered as a limited company in Hå, Rogaland with organisation number 920956270. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 50000 shares. The company's stated purpose is: “Oppføring, kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 708,000 in revenue and NOK 409,000 in operating profit.

Key figures · 2025

Revenue
NOK 708,000
Operating profit
NOK 409,000
Equity
NOK 907,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
2.48
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.3%
Satisfactory
Equity as a share of total capital

Who owns KRUSEMARKA EIENDOM AS?

JONASSEN INVEST AS
KRUSEMARKA EIENDOM AS
NOK 708,000 rev. · NOK 409,000 profit

KRUSEMARKA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRUSEMARKA EIENDOM AS

Who owns KRUSEMARKA EIENDOM AS?

JONASSEN INVEST AS is the largest registered owner, with 38.0%.

What is the revenue of KRUSEMARKA EIENDOM AS?

KRUSEMARKA EIENDOM AS had revenue of NOK 708,000 in 2025.

Who is the general manager of KRUSEMARKA EIENDOM AS?

Cato Høyland is registered as general manager of KRUSEMARKA EIENDOM AS.

Where is KRUSEMARKA EIENDOM AS based?

KRUSEMARKA EIENDOM AS has its business address in Nærbø.

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.