BIZTRAC BETA
Business and other management consultancy activities

EBHR AS

Org. no. 925136174 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 33.7m
Operating profit NOK −44,000
Equity NOK 4.1m
Incorporated 2020
Employees 11
Share capital NOK 900,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EBHR AS is registered as a limited company in Oslo, Oslo with organisation number 925136174. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020 and has 11 registered employees. Registered share capital is NOK 900,000, divided into 100 shares. The company's stated purpose is: “Kjøp/salg av eiendom, kjøp/salg av aksjer samt alt som naturlig faller herunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.7m in revenue and NOK −44,000 in operating profit.

Key figures · 2024

Revenue
NOK 33.7m
Operating profit
NOK −44,000
Equity
NOK 4.1m
Est. value
NOK 37.4m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.0%
Good
Equity as a share of total capital

Who owns EBHR AS?

SKUT VENTURE AS
EBHR AS
NOK 33.7m rev. · NOK −44,000 profit

EBHR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EBHR AS

Who owns EBHR AS?

SKUT VENTURE AS is the largest registered owner, with 100.0%.

What is the revenue of EBHR AS?

EBHR AS had revenue of NOK 33.7m in 2024.

Who is the general manager of EBHR AS?

Thomas Hoff is registered as general manager of EBHR AS.

Where is EBHR AS based?

EBHR AS has its business address in Oslo.

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.