BIZTRAC BETA
Landscape service activities

AGAIA AS

Org. no. 942493894 Limited company (AS) Drammen Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 715.1m
Operating profit NOK 29.8m
Equity NOK 88.0m
Incorporated 1987
Employees 207
Share capital NOK 3.4m

Signals

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

AGAIA AS is registered as a limited company in Drammen, Buskerud with organisation number 942493894. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 1987 and has 207 registered employees. Registered share capital is NOK 3.4m, divided into 3448459 shares. The company's stated purpose is: “Å drive handle, tjenesteyting og entreprenørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 715.1m in revenue and NOK 29.8m in operating profit.

Key figures · 2025

Revenue
NOK 715.1m
Operating profit
NOK 29.8m
Equity
NOK 88.0m
Est. value
NOK 153.0m

Financial health · 2025

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

Who owns AGAIA AS?

AGAIA GROUP AS
AGAIA AS
NOK 715.1m rev. · NOK 29.8m profit

AGAIA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does AGAIA AS own?

AGAIA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about AGAIA AS

Who owns AGAIA AS?

AGAIA GROUP AS is the largest registered owner, with 88.8%.

What is the revenue of AGAIA AS?

AGAIA AS had revenue of NOK 715.1m in 2025.

Who is the general manager of AGAIA AS?

Petter Alexander Vistnes is registered as general manager of AGAIA AS.

Where is AGAIA AS based?

AGAIA AS has its business address in Drammen.

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.