BIZTRAC BETA
COMPANY REGISTER PROFILE
936343503 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

HYPERTRO AS

Org. no. 936343503 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK 521
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-14.

HYPERTRO AS is registered as a limited company in Oslo, Oslo with organisation number 936343503. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling av app for trening, helse og kosthold med planer og abonnement.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK 521 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK 521
Equity
NOK 24,000
Est. value
NOK 15,000

Financial health · 2025

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

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

Who owns HYPERTRO AS?

MACIEJ PIOTR GLOWACKI
HYPERTRO AS
NOK 5,000 rev. · NOK 521 profit

HYPERTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HYPERTRO AS

Who owns HYPERTRO AS?

MACIEJ PIOTR GLOWACKI is the largest registered owner, with 100.0%.

What is the revenue of HYPERTRO AS?

HYPERTRO AS had revenue of NOK 5,000 in 2025.

Who is the general manager of HYPERTRO AS?

Maciej Piotr Glowacki is registered as general manager of HYPERTRO AS.

Where is HYPERTRO AS based?

HYPERTRO 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 15.06.2026.

Report a problem

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