BIZTRAC BETA
Electrical installation

VIRIDIS AS

Org. no. 925084093 Limited company (AS) Sarpsborg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 201,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VIRIDIS AS is registered as a limited company in Sarpsborg, Østfold with organisation number 925084093. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper, investering i fast eiendom og annen næringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 201,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 201,000
Equity
NOK 2.3m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns VIRIDIS AS?

H.A.G HOLDING AS
VIRIDIS AS
NOK 1.2m rev. · NOK 201,000 profit

VIRIDIS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VIRIDIS AS own?

VIRIDIS AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

VIRIDIS AS er morselskap for 7 datterselskaper:

Frequently asked questions about VIRIDIS AS

Who owns VIRIDIS AS?

H.A.G HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VIRIDIS AS?

VIRIDIS AS had revenue of NOK 1.2m in 2024.

Where is VIRIDIS AS based?

VIRIDIS 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.