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

OTTADALEN BEGRAVELSESBYRÅ NUF

Org. no. 989541412 Norwegian division of foreign business enterprise (NUF) Vågå Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 110,000
Equity NOK 53,000

OTTADALEN BEGRAVELSESBYRÅ NUF is registered as a norwegian division of foreign business enterprise in Vågå, Innlandet with organisation number 989541412. The business is classified under funeral and related activities (NACE 96.300). The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 110,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +38 %
Operating profit
NOK 110,000
▲ +205 %
Equity
NOK 53,000
▲ +197 %
Est. value
NOK 312,000

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
42.3%
Very good
Return on total assets
Solidity
16.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OTTADALEN BEGRAVELSESBYRÅ NUF?

No shareholders are registered for OTTADALEN BEGRAVELSESBYRÅ NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does OTTADALEN BEGRAVELSESBYRÅ NUF own?

OTTADALEN BEGRAVELSESBYRÅ NUF holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OTTADALEN BEGRAVELSESBYRÅ NUF

What is the revenue of OTTADALEN BEGRAVELSESBYRÅ NUF?

OTTADALEN BEGRAVELSESBYRÅ NUF had revenue of NOK 1.8m in 2025.

Who is the general manager of OTTADALEN BEGRAVELSESBYRÅ NUF?

Emil Bjarne Rustad is registered as general manager of OTTADALEN BEGRAVELSESBYRÅ NUF.

Where is OTTADALEN BEGRAVELSESBYRÅ NUF based?

OTTADALEN BEGRAVELSESBYRÅ NUF has its business address in Vågå.

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.