BIZTRAC BETA
Funeral and related activities

KONGSGAARD BEGRAVELSESBYRÅ AS

Org. no. 925123005 Limited company (AS) Notodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 604,000
Equity NOK 522,000
Incorporated 2020
Share capital NOK 30,000

KONGSGAARD BEGRAVELSESBYRÅ AS is registered as a limited company in Notodden, Telemark with organisation number 925123005. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive begravelsesbyrå og virksomhet som naturlig er forbundet med dette, samt kjøpe, selge og leie ut fast eiendom. Selskapet kan også engasjeres i annen virksomhet som kjøp og salg av aksjer eller andre verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 604,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 604,000
Equity
NOK 522,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns KONGSGAARD BEGRAVELSESBYRÅ AS?

AASE KATRINE KONGSGAARD FLAATEN
KONGSGAARD BEGRAVELSESBYRÅ AS
NOK 3.0m rev. · NOK 604,000 profit

KONGSGAARD BEGRAVELSESBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSGAARD BEGRAVELSESBYRÅ AS

Who owns KONGSGAARD BEGRAVELSESBYRÅ AS?

AASE KATRINE KONGSGAARD FLAATEN is the largest registered owner, with 100.0%.

What is the revenue of KONGSGAARD BEGRAVELSESBYRÅ AS?

KONGSGAARD BEGRAVELSESBYRÅ AS had revenue of NOK 3.0m in 2024.

Where is KONGSGAARD BEGRAVELSESBYRÅ AS based?

KONGSGAARD BEGRAVELSESBYRÅ AS has its business address in Notodden.

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.