BIZTRAC BETA
Funeral and related activities

OPSAHL BEGRAVELSESBYRÅ AS

Org. no. 926335871 Limited company (AS) Gran Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 10.2m
Operating profit NOK 3.6m
Equity NOK 4.1m
Incorporated 2020
Share capital NOK 600,000

OPSAHL BEGRAVELSESBYRÅ AS is registered as a limited company in Gran, Innlandet with organisation number 926335871. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2020. Registered share capital is NOK 600,000, divided into 1000 shares. The company's stated purpose is: “Drift av begravelsesbyrå.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.2m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 10.2m
Operating profit
NOK 3.6m
Equity
NOK 4.1m
Est. value
NOK 12.2m

Financial health · 2024

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

Who owns OPSAHL BEGRAVELSESBYRÅ AS?

LMO HOLDING AS
OPSAHL BEGRAVELSESBYRÅ AS
NOK 10.2m rev. · NOK 3.6m profit

OPSAHL BEGRAVELSESBYRÅ AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OPSAHL BEGRAVELSESBYRÅ AS own?

OPSAHL BEGRAVELSESBYRÅ AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OPSAHL BEGRAVELSESBYRÅ AS

Who owns OPSAHL BEGRAVELSESBYRÅ AS?

LMO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of OPSAHL BEGRAVELSESBYRÅ AS?

OPSAHL BEGRAVELSESBYRÅ AS had revenue of NOK 10.2m in 2024.

Who is the general manager of OPSAHL BEGRAVELSESBYRÅ AS?

Paul Arne Opsahl is registered as general manager of OPSAHL BEGRAVELSESBYRÅ AS.

Where is OPSAHL BEGRAVELSESBYRÅ AS based?

OPSAHL BEGRAVELSESBYRÅ AS has its business address in Gran.

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.