BIZTRAC BETA
COMPANY REGISTER PROFILE
933499863 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

AMPHENA AS

Org. no. 933499863 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 11,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-03-13 Adresseendring registrert 2026-03-13.

AMPHENA AS is registered as a limited company in Oslo, Oslo with organisation number 933499863. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning samt investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Former names: PA NEWCO42 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 11,000
Est. value
NOK 18,000

Financial health · 2024

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

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

Who owns AMPHENA AS?

KJETIL FOCHSEN ELLESTAD
AMPHENA AS
NOK 0 rev. · NOK −13,000 profit

AMPHENA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMPHENA AS

Who owns AMPHENA AS?

KJETIL FOCHSEN ELLESTAD is the largest registered owner, with 100.0%.

What is the revenue of AMPHENA AS?

AMPHENA AS had revenue of NOK 0 in 2025.

Where is AMPHENA AS based?

AMPHENA 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.