BIZTRAC BETA
Rental and operating of own or leased real estate

KJÆRSTAD EIENDOM AS

Org. no. 921077319 Limited company (AS) Ringsaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 842,000
Operating profit NOK 465,000
Equity NOK 3.6m
Incorporated 2018
Share capital NOK 180,000

KJÆRSTAD EIENDOM AS is registered as a limited company in Ringsaker, Innlandet with organisation number 921077319. 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 180,000, divided into 180000 shares. The company's stated purpose is: “Investering, utleie og salg av fast eiendom. Selskapet kan også investere i verdipapirer av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 842,000 in revenue and NOK 465,000 in operating profit.

Key figures · 2025

Revenue
NOK 842,000
Operating profit
NOK 465,000
Equity
NOK 3.6m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns KJÆRSTAD EIENDOM AS?

SIW MABEL JORANDA KJÆRSTAD SOLBERG
KJÆRSTAD EIENDOM AS
NOK 842,000 rev. · NOK 465,000 profit

KJÆRSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJÆRSTAD EIENDOM AS

Who owns KJÆRSTAD EIENDOM AS?

SIW MABEL JORANDA KJÆRSTAD SOLBERG is the largest registered owner, with 50.0%.

What is the revenue of KJÆRSTAD EIENDOM AS?

KJÆRSTAD EIENDOM AS had revenue of NOK 842,000 in 2025.

Who is the general manager of KJÆRSTAD EIENDOM AS?

Liv Merethe Kjærstad Bjugstad is registered as general manager of KJÆRSTAD EIENDOM AS.

Where is KJÆRSTAD EIENDOM AS based?

KJÆRSTAD EIENDOM AS has its business address in Brøttum.

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.