BIZTRAC BETA
COMPANY REGISTER PROFILE
998624347 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

BILHUSET EIENDOM AS

Org. no. 998624347 Limited company (AS) Sula Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.0m
Equity NOK 5.7m
Incorporated 2012
Share capital NOK 40,000

BILHUSET EIENDOM AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 998624347. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2012. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, samt deltakelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +9 %
Operating profit
NOK 1.0m
▲ +10 %
Equity
NOK 5.7m
▲ +14 %
Est. value
NOK 6.1m

Financial health · 2025

Liquidity
6.20
Very good
Current assets ÷ current liabilities
Profitability
14.0%
Good
Return on total assets
Solidity
70.0%
Very good
Equity as a share of total capital

Who owns BILHUSET EIENDOM AS?

BILHUSET EIENDOM AS
NOK 1.5m rev. · NOK 1.0m profit

BILHUSET EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILHUSET EIENDOM AS

Who owns BILHUSET EIENDOM AS?

ROGER SUNDE is the largest registered owner, with 50.0%.

What is the revenue of BILHUSET EIENDOM AS?

BILHUSET EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of BILHUSET EIENDOM AS?

Roger Sunde is registered as general manager of BILHUSET EIENDOM AS.

Where is BILHUSET EIENDOM AS based?

BILHUSET EIENDOM AS has its business address in Mauseidvåg.

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

Report a problem

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