BIZTRAC BETA
Computer programming activities

AGILE INTERACTIVE AS

Org. no. 916988087 Limited company (AS) Giske Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −4,000
Equity NOK 1.2m
Incorporated 2016
Share capital NOK 30,000

Signals

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

AGILE INTERACTIVE AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 916988087. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levere digitale løsninger som bedrifter skal benytte i sin kommunikasjon, både mot kunder, intern kommunikasjon og annet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −4,000
Equity
NOK 1.2m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns AGILE INTERACTIVE AS?

OLA NYGÅRD MULDAL
AGILE INTERACTIVE AS
NOK 1.9m rev. · NOK −4,000 profit

AGILE INTERACTIVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGILE INTERACTIVE AS

Who owns AGILE INTERACTIVE AS?

OLA NYGÅRD MULDAL is the largest registered owner, with 100.0%.

What is the revenue of AGILE INTERACTIVE AS?

AGILE INTERACTIVE AS had revenue of NOK 1.9m in 2025.

Who is the general manager of AGILE INTERACTIVE AS?

Ola Nygård Muldal is registered as general manager of AGILE INTERACTIVE AS.

Where is AGILE INTERACTIVE AS based?

AGILE INTERACTIVE AS has its business address in Giske.

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.