BIZTRAC BETA
Other captive investment companies

AGILE HOLDING AS

Org. no. 914599040 Limited company (AS) Nordre Follo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 904,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

AGILE HOLDING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 914599040. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer og relatert virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 904,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns AGILE HOLDING AS?

SERGIY PUSHCHIN
AGILE HOLDING AS
NOK 0 rev. · NOK −13,000 profit

AGILE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AGILE HOLDING AS own?

AGILE HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about AGILE HOLDING AS

Who owns AGILE HOLDING AS?

SERGIY PUSHCHIN is the largest registered owner, with 100.0%.

What is the revenue of AGILE HOLDING AS?

AGILE HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of AGILE HOLDING AS?

Sergiy Pushchin is registered as general manager of AGILE HOLDING AS.

Where is AGILE HOLDING AS based?

AGILE HOLDING AS has its business address in Kolbotn.

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.