BIZTRAC BETA
Funeral and related activities

RAKKESTAD BEGRAVELSESBYRÅ AS

Org. no. 916395167 Limited company (AS) Rakkestad Incorporated 1973 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 317,000
Equity NOK 1.8m
Incorporated 1973
Share capital NOK 100,000

RAKKESTAD BEGRAVELSESBYRÅ AS is registered as a limited company in Rakkestad, Østfold with organisation number 916395167. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 1973. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Begravelsesbyrå, herunder handelsvirksomhet og hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 317,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 317,000
Equity
NOK 1.8m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns RAKKESTAD BEGRAVELSESBYRÅ AS?

ANNE HILDE STØLES NESBEKK
RAKKESTAD BEGRAVELSESBYRÅ AS
NOK 3.8m rev. · NOK 317,000 profit

RAKKESTAD BEGRAVELSESBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAKKESTAD BEGRAVELSESBYRÅ AS

Who owns RAKKESTAD BEGRAVELSESBYRÅ AS?

ANNE HILDE STØLES NESBEKK is the largest registered owner, with 100.0%.

What is the revenue of RAKKESTAD BEGRAVELSESBYRÅ AS?

RAKKESTAD BEGRAVELSESBYRÅ AS had revenue of NOK 3.8m in 2025.

Who is the general manager of RAKKESTAD BEGRAVELSESBYRÅ AS?

Thea Støles Nesbekk is registered as general manager of RAKKESTAD BEGRAVELSESBYRÅ AS.

Where is RAKKESTAD BEGRAVELSESBYRÅ AS based?

RAKKESTAD BEGRAVELSESBYRÅ AS has its business address in Rakkestad.

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.