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

ASATAK AS

Org. no. 926614223 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 2.6m
Operating profit NOK 149,000
Equity NOK 215,000
Incorporated 2021
Share capital NOK 30,000

ASATAK AS is registered as a limited company in Oslo, Oslo with organisation number 926614223. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og investere i aksjer, eiendom samt andre relaterte finansielle produkter. I tillegg vil selskapet bedrive konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 149,000 in operating profit.

Former names: TORGY HYDROGEN AS, ROTOBOOST HOLDING AS

Key figures · 2025

Revenue
NOK 2.6m
▲ +15 %
Operating profit
NOK 149,000
▼ −42 %
Equity
NOK 215,000
▲ +60 %
Est. value
NOK 588,000

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
12.9%
Good
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns ASATAK AS?

ASATAK AS
NOK 2.6m rev. · NOK 149,000 profit

ASATAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASATAK AS

Who owns ASATAK AS?

Alexander Sebastian Aguilera is the largest registered owner, with 100.0%.

What is the revenue of ASATAK AS?

ASATAK AS had revenue of NOK 2.6m in 2025.

Who is the general manager of ASATAK AS?

Alexander Sebastian Aguilera is registered as general manager of ASATAK AS.

Where is ASATAK AS based?

ASATAK AS has its business address in Oslo.

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.