biztrac. BETA
COMPANY REGISTER PROFILE
997258673 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

AGLO AS

Org. no. 997258673 Limited company (AS) Stjørdal Incorporated 2011 Active
Revenue 2025 NOK 0
Operating profit NOK −58,000
Equity NOK 204,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

AGLO AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 997258673. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å yte konsulenttjenester innen økonomi og administrasjon, samt deltakelse i andre selskap og virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −58,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −58,000
▼ −612 %
Equity
NOK 204,000
▼ −20 %
Est. value
NOK 331,000

Financial health · 2025

Liquidity
50.49
Very good
Current assets ÷ current liabilities
Profitability
-22.4%
Not satisfactory
Return on total assets
Solidity
98.3%
Very good
Equity as a share of total capital

Who owns AGLO AS?

AGLO AS
NOK 0 rev. · NOK −58,000 profit

AGLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGLO AS

Who owns AGLO AS?

Johan Olav Hegge is the largest registered owner, with 100.0%.

What is the revenue of AGLO AS?

AGLO AS had revenue of NOK 0 in 2025.

Who is the general manager of AGLO AS?

Johan Olav Hegge is registered as general manager of AGLO AS.

Where is AGLO AS based?

AGLO AS has its business address in Skatval.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.