BIZTRAC BETA
Development of building projects

HOLMEN BRYGGE EIENDOM AS

Org. no. 994798952 Limited company (AS) Tønsberg Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 24,000
Operating profit NOK −24,000
Equity NOK 3.0m
Incorporated 2009
Share capital NOK 5.0m

Signals

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

HOLMEN BRYGGE EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 994798952. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 5.0m, divided into 5 shares. The company's stated purpose is: “Investere i andre selskaper og drive utvikling av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 24,000 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 24,000
Operating profit
NOK −24,000
Equity
NOK 3.0m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns HOLMEN BRYGGE EIENDOM AS?

BRATTEKLEIV INVEST AS
HOLMEN BRYGGE EIENDOM AS
NOK 24,000 rev. · NOK −24,000 profit

HOLMEN BRYGGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLMEN BRYGGE EIENDOM AS

Who owns HOLMEN BRYGGE EIENDOM AS?

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

What is the revenue of HOLMEN BRYGGE EIENDOM AS?

HOLMEN BRYGGE EIENDOM AS had revenue of NOK 24,000 in 2024.

Where is HOLMEN BRYGGE EIENDOM AS based?

HOLMEN BRYGGE EIENDOM AS has its business address in Tønsberg.

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.