BIZTRAC BETA
Publishing of books

AH MEDIA AS

Org. no. 932497158 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 387,000
Operating profit NOK −140,000
Equity NOK −5,000
Incorporated 2023
Share capital NOK 231,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−140k kr).
  • Nylig endring 2026-02-02 Aksjekapital registrert 2026-02-02.

AH MEDIA AS is registered as a limited company in Øygarden, Vestland with organisation number 932497158. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2023. Registered share capital is NOK 231,000, divided into 30 shares. The company's stated purpose is: “Forlagsvirksomhet og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 387,000 in revenue and NOK −140,000 in operating profit.

Key figures · 2025

Revenue
NOK 387,000
Operating profit
NOK −140,000
Equity
NOK −5,000

Financial health · 2025

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

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

Who owns AH MEDIA AS?

MARGIT LILJAN APELTHUN
AH MEDIA AS
NOK 387,000 rev. · NOK −140,000 profit

AH MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AH MEDIA AS

Who owns AH MEDIA AS?

MARGIT LILJAN APELTHUN is the largest registered owner, with 100.0%.

What is the revenue of AH MEDIA AS?

AH MEDIA AS had revenue of NOK 387,000 in 2025.

Who is the general manager of AH MEDIA AS?

Margit Liljan Apelthun is registered as general manager of AH MEDIA AS.

Where is AH MEDIA AS based?

AH MEDIA AS has its business address in Fjell.

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.