BIZTRAC BETA
Development of building projects

KNAPPEN EIENDOM AS

Org. no. 832836702 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −26,000
Equity NOK 80,000
Incorporated 2023
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KNAPPEN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 832836702. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, drift og forvaltning av fast eiendom, samt investere i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 80,000
Est. value
NOK 73,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KNAPPEN EIENDOM AS?

JAVE INVEST AS
KNAPPEN EIENDOM AS
NOK 0 rev. · NOK −26,000 profit

KNAPPEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNAPPEN EIENDOM AS

Who owns KNAPPEN EIENDOM AS?

JAVE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KNAPPEN EIENDOM AS?

KNAPPEN EIENDOM AS had revenue of NOK 0 in 2024.

Where is KNAPPEN EIENDOM AS based?

KNAPPEN EIENDOM AS has its business address in Nesttun.

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.