BIZTRAC BETA
Rental and operating of own or leased real estate

N PROPERTIES AS

Org. no. 931943308 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

N PROPERTIES AS is registered as a limited company in Drammen, Buskerud with organisation number 931943308. 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 100 shares. The company's stated purpose is: “Eiendomshandel og -utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 14,000
Est. value
NOK 13,000

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
971.7%
Weak
Equity as a share of total capital

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

Who owns N PROPERTIES AS?

N GRUPPEN HOLDING AS
N PROPERTIES AS
NOK 0 rev. · NOK −4,000 profit

N PROPERTIES AS has 1 registered shareholder:

All shareholders and roles →

Group structure

N PROPERTIES AS er morselskap for 3 datterselskaper:

Frequently asked questions about N PROPERTIES AS

Who owns N PROPERTIES AS?

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

What is the revenue of N PROPERTIES AS?

N PROPERTIES AS had revenue of NOK 0 in 2025.

Who is the general manager of N PROPERTIES AS?

Emil Nguyen is registered as general manager of N PROPERTIES AS.

Where is N PROPERTIES AS based?

N PROPERTIES AS has its business address in Mjøndalen.

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.