BIZTRAC BETA
Security activities n.e.c.

DIRGI AS

Org. no. 990324441 Limited company (AS) Bærum Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 732,000
Equity NOK 97.3m
Incorporated 2006
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.

DIRGI AS is registered as a limited company in Bærum, Akershus with organisation number 990324441. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå vaktvirksomhet samt montering og vedlikehold av sikkerhetsutstyr knyttet til virksomheten overfor private husholdinger, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 732,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 732,000
Equity
NOK 97.3m
Est. value
NOK 51.2m

Financial health · 2024

Liquidity
65.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
58.6%
Very good
Equity as a share of total capital

Who owns DIRGI AS?

ARE SMUK FIGVED
DIRGI AS
NOK 2.3m rev. · NOK 732,000 profit

DIRGI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIRGI AS own?

DIRGI AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about DIRGI AS

Who owns DIRGI AS?

ARE SMUK FIGVED is the largest registered owner, with 100.0%.

What is the revenue of DIRGI AS?

DIRGI AS had revenue of NOK 2.3m in 2024.

Where is DIRGI AS based?

DIRGI AS has its business address in Blommenholm.

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.