biztrac. BETA
COMPANY REGISTER PROFILE
933250547 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VIRIDIS EIENDOM AS

Org. no. 933250547 Limited company (AS) Sarpsborg Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 4.1m
Incorporated 2024
Share capital NOK 4.0m

Signals

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

VIRIDIS EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 933250547. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 4.0m, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, samt eie aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 4.1m
▲ +3 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.7%
Weak
Return on total assets
Solidity
59.5%
Very good
Equity as a share of total capital

Who owns VIRIDIS EIENDOM AS?

VIRIDIS EIENDOM AS
NOK 0 rev. · NOK −8,000 profit

VIRIDIS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIRIDIS EIENDOM AS own?

VIRIDIS EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

VIRIDIS EIENDOM AS er morselskap for 7 datterselskaper:

Frequently asked questions about VIRIDIS EIENDOM AS

Who owns VIRIDIS EIENDOM AS?

VIRIDIS AS is the largest registered owner, with 100.0%.

What is the revenue of VIRIDIS EIENDOM AS?

VIRIDIS EIENDOM AS had revenue of NOK 0 in 2025.

Where is VIRIDIS EIENDOM AS based?

VIRIDIS EIENDOM AS has its business address in Grålum.

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.