BIZTRAC BETA
Publishing of newspapers

HANDELSAVISEN AS

Org. no. 932297922 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 12,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

HANDELSAVISEN AS is registered as a limited company in Oslo, Oslo with organisation number 932297922. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Avis og forlagsvirksomhet, og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 12,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns HANDELSAVISEN AS?

WOL INDUSTRIES AS
HANDELSAVISEN AS
NOK 0 rev. · NOK −7,000 profit

HANDELSAVISEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HANDELSAVISEN AS er morselskap for 1 datterselskap:

Frequently asked questions about HANDELSAVISEN AS

Who owns HANDELSAVISEN AS?

WOL INDUSTRIES AS is the largest registered owner, with 100.0%.

What is the revenue of HANDELSAVISEN AS?

HANDELSAVISEN AS had revenue of NOK 0 in 2024.

Who is the general manager of HANDELSAVISEN AS?

Oskar Andreas Berg is registered as general manager of HANDELSAVISEN AS.

Where is HANDELSAVISEN AS based?

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