BIZTRAC BETA
Site preparation

HEB ENTREPRENØR AS

Org. no. 914075424 Limited company (AS) Horten Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 18.5m
Operating profit NOK 3.1m
Equity NOK 3.7m
Incorporated 2014
Employees 6
Share capital NOK 2.3m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEB ENTREPRENØR AS is registered as a limited company in Horten, Vestfold with organisation number 914075424. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 2.3m, divided into 234306 shares. The company's stated purpose is: “Anleggsvirksomhet, prosjektadministrasjon samt annen virksomhet som har naturlig forbindelse med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.5m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 18.5m
Operating profit
NOK 3.1m
Equity
NOK 3.7m
Est. value
NOK 11.0m

Financial health · 2025

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

Who owns HEB ENTREPRENØR AS?

HEB AS
HEB ENTREPRENØR AS
NOK 18.5m rev. · NOK 3.1m profit

HEB ENTREPRENØR AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEB ENTREPRENØR AS

Who owns HEB ENTREPRENØR AS?

HEB AS is the largest registered owner, with 82.6%.

What is the revenue of HEB ENTREPRENØR AS?

HEB ENTREPRENØR AS had revenue of NOK 18.5m in 2025.

Who is the general manager of HEB ENTREPRENØR AS?

Hans-Erik Becker is registered as general manager of HEB ENTREPRENØR AS.

Where is HEB ENTREPRENØR AS based?

HEB ENTREPRENØR AS has its business address in Horten.

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.