biztrac. BETA
COMPANY REGISTER PROFILE
987291184 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HOPSNESVEIEN 21 AS

Org. no. 987291184 Limited company (AS) Bergen Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 520,000
Equity NOK 5.1m
Incorporated 2004
Share capital NOK 4.0m

Signals

1 flags
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

HOPSNESVEIEN 21 AS is registered as a limited company in Bergen, Vestland with organisation number 987291184. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 4.0m, divided into 40000 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 2025 financial year, show NOK 1.1m in revenue and NOK 520,000 in operating profit.

Former names: HOPNESVEIEN 21 AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +0 %
Operating profit
NOK 520,000
▼ −3 %
Equity
NOK 5.1m
▼ −0 %
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
81.0%
Very good
Equity as a share of total capital

Who owns HOPSNESVEIEN 21 AS?

HOPSNESVEIEN 21 AS
NOK 1.1m rev. · NOK 520,000 profit

HOPSNESVEIEN 21 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOPSNESVEIEN 21 AS

Who owns HOPSNESVEIEN 21 AS?

HOPSNESVEIEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HOPSNESVEIEN 21 AS?

HOPSNESVEIEN 21 AS had revenue of NOK 1.1m in 2025.

Where is HOPSNESVEIEN 21 AS based?

HOPSNESVEIEN 21 AS has its business address in Paradis.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.