BIZTRAC BETA
Buying and selling of own real estate

KROKRYGG EIENDOM AS

Org. no. 920013252 Limited company (AS) Eidsvoll Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 550,000
Operating profit NOK 98,000
Equity NOK 271,000
Incorporated 2017
Share capital NOK 300,000

KROKRYGG EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 920013252. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Investering i, utvikling og salg av fast eiendom, samt drift av disse, og det som herved står i naturlig forbindelse, herunder aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 550,000 in revenue and NOK 98,000 in operating profit.

Key figures · 2024

Revenue
NOK 550,000
Operating profit
NOK 98,000
Equity
NOK 271,000
Est. value
NOK 356,000

Financial health · 2024

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

Who owns KROKRYGG EIENDOM AS?

MINNESUNDSENTERET AS
KROKRYGG EIENDOM AS
NOK 550,000 rev. · NOK 98,000 profit

KROKRYGG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KROKRYGG EIENDOM AS own?

KROKRYGG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KROKRYGG EIENDOM AS

Who owns KROKRYGG EIENDOM AS?

MINNESUNDSENTERET AS is the largest registered owner, with 34.0%.

What is the revenue of KROKRYGG EIENDOM AS?

KROKRYGG EIENDOM AS had revenue of NOK 550,000 in 2024.

Where is KROKRYGG EIENDOM AS based?

KROKRYGG EIENDOM AS has its business address in Minnesund.

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.