BIZTRAC BETA
Development of building projects

NORSK NÆRINGSEIENDOM AS

Org. no. 928625087 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK −45,000
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).

NORSK NÆRINGSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 928625087. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av eiendom, eiendomsutvikling, samt deltakelse i eiendomsprosjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 120,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK −45,000
Equity
NOK 30,000
Est. value
NOK 201,000

Financial health · 2024

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

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

Who owns NORSK NÆRINGSEIENDOM AS?

PETTER RUUD
NORSK NÆRINGSEIENDOM AS
NOK 120,000 rev. · NOK −45,000 profit

NORSK NÆRINGSEIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Group structure

NORSK NÆRINGSEIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about NORSK NÆRINGSEIENDOM AS

Who owns NORSK NÆRINGSEIENDOM AS?

PETTER RUUD is the largest registered owner, with 50.0%.

What is the revenue of NORSK NÆRINGSEIENDOM AS?

NORSK NÆRINGSEIENDOM AS had revenue of NOK 120,000 in 2024.

Where is NORSK NÆRINGSEIENDOM AS based?

NORSK NÆRINGSEIENDOM AS has its business address in Oslo.

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.