BIZTRAC BETA
Rental and operating of own or leased real estate

KOKSTAD PROPERTY AS

Org. no. 914408903 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 3.7m
Equity NOK 1.7m
Incorporated 2014
Share capital NOK 100,000

Signals

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

KOKSTAD PROPERTY AS is registered as a limited company in Bergen, Vestland with organisation number 914408903. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Investering, kjøp, salg, forvaltning, drift, utvikling og utleie av fast eiendom, samt å eie aksjer i andre selskaper, og alt hva der står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 3.7m
Equity
NOK 1.7m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns KOKSTAD PROPERTY AS?

WEST COAST INVEST EIENDOM AS
KOKSTAD PROPERTY AS
NOK 4.3m rev. · NOK 3.7m profit

KOKSTAD PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOKSTAD PROPERTY AS

Who owns KOKSTAD PROPERTY AS?

WEST COAST INVEST EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KOKSTAD PROPERTY AS?

KOKSTAD PROPERTY AS had revenue of NOK 4.3m in 2024.

Where is KOKSTAD PROPERTY AS based?

KOKSTAD PROPERTY AS has its business address in Kokstad.

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.