BIZTRAC BETA
Rental and operating of own or leased real estate

NYPLASSEN EIENDOM AS

Org. no. 931481304 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK −2.5m
Equity NOK −3.1m
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,5 mill kr).

NYPLASSEN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 931481304. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Direkte og indirekte investeringer i fast eiendom, samt naturlig tilknyttede aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK −2.5m in operating profit.

Key figures · 2025

Revenue
NOK 160,000
Operating profit
NOK −2.5m
Equity
NOK −3.1m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-34.8%
Weak
Equity as a share of total capital

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

Who owns NYPLASSEN EIENDOM AS?

HOPE EIENDOM AS
NYPLASSEN EIENDOM AS
NOK 160,000 rev. · NOK −2.5m profit

NYPLASSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYPLASSEN EIENDOM AS

Who owns NYPLASSEN EIENDOM AS?

HOPE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NYPLASSEN EIENDOM AS?

NYPLASSEN EIENDOM AS had revenue of NOK 160,000 in 2025.

Where is NYPLASSEN EIENDOM AS based?

NYPLASSEN EIENDOM AS has its business address in Øvre Ervik.

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.