biztrac. BETA
COMPANY REGISTER PROFILE
929447336 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Funeral and related activities

KINN BEGRAVELSESBYRÅ AS

Org. no. 929447336 Limited company (AS) Kinn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 183,000
Equity NOK 565,000
Incorporated 2022
Share capital NOK 500,000

KINN BEGRAVELSESBYRÅ AS is registered as a limited company in Kinn, Vestland with organisation number 929447336. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Drive begravelsesbyrå samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 183,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▼ −9 %
Operating profit
NOK 183,000
▼ −64 %
Equity
NOK 565,000
▼ −21 %
Est. value
NOK 989,000

Financial health · 2025

Liquidity
2.98
Very good
Current assets ÷ current liabilities
Profitability
9.0%
Satisfactory
Return on total assets
Solidity
28.7%
Good
Equity as a share of total capital

Who owns KINN BEGRAVELSESBYRÅ AS?

KINN BEGRAVELSESBYRÅ AS
NOK 2.8m rev. · NOK 183,000 profit

KINN BEGRAVELSESBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KINN BEGRAVELSESBYRÅ AS

Who owns KINN BEGRAVELSESBYRÅ AS?

Nina Øen-Gundersen is the largest registered owner, with 100.0%.

What is the revenue of KINN BEGRAVELSESBYRÅ AS?

KINN BEGRAVELSESBYRÅ AS had revenue of NOK 2.8m in 2025.

Who is the general manager of KINN BEGRAVELSESBYRÅ AS?

Nina Øen-Gundersen is registered as general manager of KINN BEGRAVELSESBYRÅ AS.

Where is KINN BEGRAVELSESBYRÅ AS based?

KINN BEGRAVELSESBYRÅ AS has its business address in Florø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.