BIZTRAC BETA
Publishing of newspapers

SYNSTE MØRE AS

Org. no. 921709242 Limited company (AS) Vanylven Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 182,000
Equity NOK 1.3m
Incorporated 2018
Employees 5
Share capital NOK 150,000

Signals

1 flags
  • Nylig endring 2026-03-27 Adresseendring registrert 2026-03-27.

SYNSTE MØRE AS is registered as a limited company in Vanylven, Møre og Romsdal with organisation number 921709242. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 30 shares. The company's stated purpose is: “Utgjevar av lokalavis i Vanylven kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 182,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 182,000
Equity
NOK 1.3m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns SYNSTE MØRE AS?

SIGVE SLAGNES
SYNSTE MØRE AS
NOK 4.4m rev. · NOK 182,000 profit

SYNSTE MØRE AS has 9 registered shareholders:

All shareholders and roles →

Which companies does SYNSTE MØRE AS own?

SYNSTE MØRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYNSTE MØRE AS

Who owns SYNSTE MØRE AS?

SIGVE SLAGNES is the largest registered owner, with 20.0%.

What is the revenue of SYNSTE MØRE AS?

SYNSTE MØRE AS had revenue of NOK 4.4m in 2025.

Who is the general manager of SYNSTE MØRE AS?

Rønnaug Søvik is registered as general manager of SYNSTE MØRE AS.

Where is SYNSTE MØRE AS based?

SYNSTE MØRE AS has its business address in Fiskå.

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.