BIZTRAC BETA
Rental and operating of own or leased real estate

KOKKEPLASSEN EIENDOM AS

Org. no. 989986902 Limited company (AS) Grimstad Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 26.4m
Operating profit NOK 9.9m
Equity NOK 9.4m
Incorporated 2006
Share capital NOK 600,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KOKKEPLASSEN EIENDOM AS is registered as a limited company in Grimstad, Agder with organisation number 989986902. 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 600,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 26.4m in revenue and NOK 9.9m in operating profit.

Key figures · 2024

Revenue
NOK 26.4m
Operating profit
NOK 9.9m
Equity
NOK 9.4m
Est. value
NOK 30.6m

Financial health · 2024

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

Who owns KOKKEPLASSEN EIENDOM AS?

J. B. UGLAND EIENDOMSUTVIKLING
KOKKEPLASSEN EIENDOM AS
NOK 26.4m rev. · NOK 9.9m profit

KOKKEPLASSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOKKEPLASSEN EIENDOM AS

Who owns KOKKEPLASSEN EIENDOM AS?

J. B. UGLAND EIENDOMSUTVIKLING is the largest registered owner, with 100.0%.

What is the revenue of KOKKEPLASSEN EIENDOM AS?

KOKKEPLASSEN EIENDOM AS had revenue of NOK 26.4m in 2024.

Where is KOKKEPLASSEN EIENDOM AS based?

KOKKEPLASSEN EIENDOM AS has its business address in Grimstad.

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.