BIZTRAC BETA
Other real estate activities on a fee or contract basis

COOP RAKKESTAD EIENDOM AS

Org. no. 830807802 Limited company (AS) Nordre Follo Incorporated 1975 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 431,000
Equity NOK 3.9m
Incorporated 1975
Share capital NOK 100,000

COOP RAKKESTAD EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 830807802. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1975. Registered share capital is NOK 100,000, divided into 100 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 2024 financial year, show NOK 1.4m in revenue and NOK 431,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 431,000
Equity
NOK 3.9m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns COOP RAKKESTAD EIENDOM AS?

COOP ØST SA
COOP RAKKESTAD EIENDOM AS
NOK 1.4m rev. · NOK 431,000 profit

COOP RAKKESTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COOP RAKKESTAD EIENDOM AS

Who owns COOP RAKKESTAD EIENDOM AS?

COOP ØST SA is the largest registered owner, with 100.0%.

What is the revenue of COOP RAKKESTAD EIENDOM AS?

COOP RAKKESTAD EIENDOM AS had revenue of NOK 1.4m in 2024.

Who is the general manager of COOP RAKKESTAD EIENDOM AS?

Vemund Kongsnes is registered as general manager of COOP RAKKESTAD EIENDOM AS.

Where is COOP RAKKESTAD EIENDOM AS based?

COOP RAKKESTAD EIENDOM AS has its business address in Kolbotn.

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.