BIZTRAC BETA
Funeral and related activities

SØRE SUNNMØRE GRAVFERDSBYRÅ AS

Org. no. 831175362 Limited company (AS) Herøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 2.1m
Equity NOK 1.8m
Incorporated 2023
Share capital NOK 30,000

SØRE SUNNMØRE GRAVFERDSBYRÅ AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 831175362. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Gravferdstjenester, drift av begravelsesbyrå samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 2.1m
Equity
NOK 1.8m
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns SØRE SUNNMØRE GRAVFERDSBYRÅ AS?

FRANK OTTO KVALSVIK
SØRE SUNNMØRE GRAVFERDSBYRÅ AS
NOK 5.0m rev. · NOK 2.1m profit

SØRE SUNNMØRE GRAVFERDSBYRÅ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRE SUNNMØRE GRAVFERDSBYRÅ AS

Who owns SØRE SUNNMØRE GRAVFERDSBYRÅ AS?

FRANK OTTO KVALSVIK is the largest registered owner, with 60.0%.

What is the revenue of SØRE SUNNMØRE GRAVFERDSBYRÅ AS?

SØRE SUNNMØRE GRAVFERDSBYRÅ AS had revenue of NOK 5.0m in 2025.

Who is the general manager of SØRE SUNNMØRE GRAVFERDSBYRÅ AS?

Frank Otto Kvalsvik is registered as general manager of SØRE SUNNMØRE GRAVFERDSBYRÅ AS.

Where is SØRE SUNNMØRE GRAVFERDSBYRÅ AS based?

SØRE SUNNMØRE GRAVFERDSBYRÅ AS has its business address in Fosnavåg.

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.