BIZTRAC BETA
Growing of other non-perennial crops

KORSVIK BEGRAVELSESBYRÅ AS

Org. no. 982851432 Limited company (AS) Sandefjord Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 733,000
Equity NOK 10.3m
Incorporated 2001
Share capital NOK 300,000

KORSVIK BEGRAVELSESBYRÅ AS is registered as a limited company in Sandefjord, Vestfold with organisation number 982851432. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2001. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drift av begravelsesbyrå og det som naturlig hører sammen med dette, herunder også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 733,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 733,000
Equity
NOK 10.3m
Est. value
NOK 7.6m

Financial health · 2025

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

Who owns KORSVIK BEGRAVELSESBYRÅ AS?

ODDBJØRN KORSVIK
KORSVIK BEGRAVELSESBYRÅ AS
NOK 3.9m rev. · NOK 733,000 profit

KORSVIK BEGRAVELSESBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KORSVIK BEGRAVELSESBYRÅ AS

Who owns KORSVIK BEGRAVELSESBYRÅ AS?

ODDBJØRN KORSVIK is the largest registered owner, with 100.0%.

What is the revenue of KORSVIK BEGRAVELSESBYRÅ AS?

KORSVIK BEGRAVELSESBYRÅ AS had revenue of NOK 3.9m in 2025.

Who is the general manager of KORSVIK BEGRAVELSESBYRÅ AS?

Oddbjørn Korsvik is registered as general manager of KORSVIK BEGRAVELSESBYRÅ AS.

Where is KORSVIK BEGRAVELSESBYRÅ AS based?

KORSVIK BEGRAVELSESBYRÅ AS has its business address in Sandefjord.

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.