BIZTRAC BETA
Business and other management consultancy activities

AEGILON AS

Org. no. 988453196 Limited company (AS) Senja Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 1.7m
Equity NOK −2.2m
Incorporated 2005
Share capital NOK 276,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,2 mill kr).

AEGILON AS is registered as a limited company in Senja, Troms with organisation number 988453196. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 276,000, divided into 2760000 shares. The company's stated purpose is: “Selskapets virksomhet er: Konsulenttjenester, prosjekteringstjenester, investeringer og kjøp og salg av verdipapirer, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 1.7m
Equity
NOK −2.2m
Est. value
NOK 7.9m

Financial health · 2024

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-164.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AEGILON AS?

AEGILON PTE LTD.
AEGILON AS
NOK 2.5m rev. · NOK 1.7m profit

AEGILON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AEGILON AS own?

AEGILON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AEGILON AS

Who owns AEGILON AS?

AEGILON PTE LTD. is the largest registered owner, with 100.0%.

What is the revenue of AEGILON AS?

AEGILON AS had revenue of NOK 2.5m in 2024.

Where is AEGILON AS based?

AEGILON AS has its business address in Finnsnes.

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.