BIZTRAC BETA
Funeral and related activities

KIØSTERUD BEGRAVELSESBYRÅ AS

Org. no. 926515128 Limited company (AS) Bamble Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 8.0m
Operating profit NOK 348,000
Equity NOK 2.2m
Incorporated 2021
Share capital NOK 100,000

KIØSTERUD BEGRAVELSESBYRÅ AS is registered as a limited company in Bamble, Telemark with organisation number 926515128. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av begravelsesbyrå samt andre formål som naturlig hører inn under slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.0m in revenue and NOK 348,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.0m
Operating profit
NOK 348,000
Equity
NOK 2.2m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns KIØSTERUD BEGRAVELSESBYRÅ AS?

ARNFINN JOHNSEN FINMARK
KIØSTERUD BEGRAVELSESBYRÅ AS
NOK 8.0m rev. · NOK 348,000 profit

KIØSTERUD BEGRAVELSESBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KIØSTERUD BEGRAVELSESBYRÅ AS own?

KIØSTERUD BEGRAVELSESBYRÅ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KIØSTERUD BEGRAVELSESBYRÅ AS

Who owns KIØSTERUD BEGRAVELSESBYRÅ AS?

ARNFINN JOHNSEN FINMARK is the largest registered owner, with 100.0%.

What is the revenue of KIØSTERUD BEGRAVELSESBYRÅ AS?

KIØSTERUD BEGRAVELSESBYRÅ AS had revenue of NOK 8.0m in 2024.

Where is KIØSTERUD BEGRAVELSESBYRÅ AS based?

KIØSTERUD BEGRAVELSESBYRÅ AS has its business address in Stathelle.

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.