BIZTRAC BETA
Other specialised construction activities n.e.c.

BHE SERVICE AS

Org. no. 927246503 Limited company (AS) Stad Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 221,000
Operating profit NOK 31,000
Equity NOK 131,000
Incorporated 2021
Share capital NOK 30,000

BHE SERVICE AS is registered as a limited company in Stad, Vestland with organisation number 927246503. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen betong og murimpregnering. Reperasjon og utleie av diverse ting og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 221,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2025

Revenue
NOK 221,000
Operating profit
NOK 31,000
Equity
NOK 131,000
Est. value
NOK 162,000

Financial health · 2025

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

Who owns BHE SERVICE AS?

BJØRN HENNING EIDE
BHE SERVICE AS
NOK 221,000 rev. · NOK 31,000 profit

BHE SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BHE SERVICE AS

Who owns BHE SERVICE AS?

BJØRN HENNING EIDE is the largest registered owner, with 100.0%.

What is the revenue of BHE SERVICE AS?

BHE SERVICE AS had revenue of NOK 221,000 in 2025.

Who is the general manager of BHE SERVICE AS?

Bjørn Henning Eide is registered as general manager of BHE SERVICE AS.

Where is BHE SERVICE AS based?

BHE SERVICE AS has its business address in Bryggja.

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.