BIZTRAC BETA
Funeral and related activities

LANGLEITE BEGRAVELSESBYRÅ AS

Org. no. 931844539 Limited company (AS) Alvdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK 1.1m
Equity NOK 875,000
Incorporated 2023
Share capital NOK 30,000

LANGLEITE BEGRAVELSESBYRÅ AS is registered as a limited company in Alvdal, Innlandet with organisation number 931844539. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Planlegging og gjennomføring av begravelser. Transport av kister, bårer og utstyr. Salg av tjenester knyttet til begravelsesbyrå.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK 1.1m
Equity
NOK 875,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns LANGLEITE BEGRAVELSESBYRÅ AS?

BIRK LANGLEITE
LANGLEITE BEGRAVELSESBYRÅ AS
NOK 5.9m rev. · NOK 1.1m profit

LANGLEITE BEGRAVELSESBYRÅ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANGLEITE BEGRAVELSESBYRÅ AS

Who owns LANGLEITE BEGRAVELSESBYRÅ AS?

BIRK LANGLEITE is the largest registered owner, with 33.3%.

What is the revenue of LANGLEITE BEGRAVELSESBYRÅ AS?

LANGLEITE BEGRAVELSESBYRÅ AS had revenue of NOK 5.9m in 2024.

Who is the general manager of LANGLEITE BEGRAVELSESBYRÅ AS?

Andrine Linnéa Langleite is registered as general manager of LANGLEITE BEGRAVELSESBYRÅ AS.

Where is LANGLEITE BEGRAVELSESBYRÅ AS based?

LANGLEITE BEGRAVELSESBYRÅ AS has its business address in Alvdal.

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.