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

HVIDING EIENDOM AS

Org. no. 912874281 Limited company (AS) Stavanger Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.4m
Equity NOK 3.3m
Incorporated 1976
Share capital NOK 200,000

HVIDING EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 912874281. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 1976. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eie, forvaltning og utleie av fast eiendom, eie og delta i andre selskaper, drive begravelsesbyrå, produksjon - handel samt hva dermed står i for- bindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
▼ −8 %
Operating profit
NOK 1.4m
▼ −27 %
Equity
NOK 3.3m
▲ +3 %
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns HVIDING EIENDOM AS?

HVIDING EIENDOM AS
NOK 2.6m rev. · NOK 1.4m profit

HVIDING EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HVIDING EIENDOM AS

Who owns HVIDING EIENDOM AS?

BALEDO AS is the largest registered owner, with 100.0%.

What is the revenue of HVIDING EIENDOM AS?

HVIDING EIENDOM AS had revenue of NOK 2.6m in 2025.

Who is the general manager of HVIDING EIENDOM AS?

Bjørn Hviding is registered as general manager of HVIDING EIENDOM AS.

Where is HVIDING EIENDOM AS based?

HVIDING EIENDOM AS has its business address in Stavanger.

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.