BIZTRAC BETA
COMPANY REGISTER PROFILE
933115046 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

NOVI EIENDOM AS

Org. no. 933115046 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 66,000
Equity NOK 48,000
Incorporated 2024
Share capital NOK 30,000

NOVI EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 933115046. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Generelle bygg- og oppussing tjenester. Rehabilitering av bygninger ut- og innvendig. Renholdstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 66,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 66,000
Equity
NOK 48,000
Est. value
NOK 246,000

Financial health · 2025

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

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

Who owns NOVI EIENDOM AS?

MARCIN DUDA
NOVI EIENDOM AS
NOK 2.1m rev. · NOK 66,000 profit

NOVI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOVI EIENDOM AS

Who owns NOVI EIENDOM AS?

MARCIN DUDA is the largest registered owner, with 100.0%.

What is the revenue of NOVI EIENDOM AS?

NOVI EIENDOM AS had revenue of NOK 2.1m in 2025.

Who is the general manager of NOVI EIENDOM AS?

Marcin Duda is registered as general manager of NOVI EIENDOM AS.

Where is NOVI EIENDOM AS based?

NOVI EIENDOM 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.