BIZTRAC BETA
Rental and operating of own or leased real estate

HOLMESTRANDGATEN 23 AS

Org. no. 996783146 Limited company (AS) Holmestrand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 108,000
Operating profit NOK 52,000
Equity NOK 135,000
Incorporated 2011
Share capital NOK 100,000

HOLMESTRANDGATEN 23 AS is registered as a limited company in Holmestrand, Vestfold with organisation number 996783146. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie, drift og salg av eiendommer og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 108,000 in revenue and NOK 52,000 in operating profit.

Key figures · 2025

Revenue
NOK 108,000
Operating profit
NOK 52,000
Equity
NOK 135,000
Est. value
NOK 223,000

Financial health · 2025

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

Who owns HOLMESTRANDGATEN 23 AS?

NEVA EIENDOM AS
HOLMESTRANDGATEN 23 AS
NOK 108,000 rev. · NOK 52,000 profit

HOLMESTRANDGATEN 23 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOLMESTRANDGATEN 23 AS

Who owns HOLMESTRANDGATEN 23 AS?

NEVA EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of HOLMESTRANDGATEN 23 AS?

HOLMESTRANDGATEN 23 AS had revenue of NOK 108,000 in 2025.

Where is HOLMESTRANDGATEN 23 AS based?

HOLMESTRANDGATEN 23 AS has its business address in Holmestrand.

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.