BIZTRAC BETA
Publishing of newspapers

FISKERIBLADET AS

Org. no. 911650924 Limited company (AS) Bergen Incorporated 1930 Active
Ownership graph ↗
Revenue 2024 NOK 35.6m
Operating profit NOK −4.0m
Equity NOK 30.2m
Incorporated 1930
Employees 12
Share capital NOK 184,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,0 mill kr).
  • Nylig endring 2026-03-31 Adresseendring registrert 2026-03-31.

FISKERIBLADET AS is registered as a limited company in Bergen, Vestland with organisation number 911650924. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 1930 and has 12 registered employees. Registered share capital is NOK 184,000, divided into 1000 shares. The company's stated purpose is: “Utgi avisen Fiskeribladet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.6m in revenue and NOK −4.0m in operating profit.

Key figures · 2024

Revenue
NOK 35.6m
Operating profit
NOK −4.0m
Equity
NOK 30.2m
Est. value
NOK 73.2m

Financial health · 2024

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

Who owns FISKERIBLADET AS?

DN MEDIA GROUP AS
FISKERIBLADET AS
NOK 35.6m rev. · NOK −4.0m profit

FISKERIBLADET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISKERIBLADET AS

Who owns FISKERIBLADET AS?

DN MEDIA GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of FISKERIBLADET AS?

FISKERIBLADET AS had revenue of NOK 35.6m in 2024.

Who is the general manager of FISKERIBLADET AS?

Øystein Hage is registered as general manager of FISKERIBLADET AS.

Where is FISKERIBLADET AS based?

FISKERIBLADET AS has its business address in Bergen.

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.