BIZTRAC BETA
Dental practice care activities

EVHAHN AS

Org. no. 935460018 Limited company (AS) Steinkjer Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK −106,000
Equity NOK −57,000
Incorporated 2025
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−57k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

EVHAHN AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 935460018. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive tannlegevirksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK −106,000
Equity
NOK −57,000

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EVHAHN AS?

ESPEN VEKSETH-HAHN
EVHAHN AS
NOK 6.8m rev. · NOK −106,000 profit

EVHAHN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVHAHN AS

Who owns EVHAHN AS?

ESPEN VEKSETH-HAHN is the largest registered owner, with 100.0%.

What is the revenue of EVHAHN AS?

EVHAHN AS had revenue of NOK 6.8m in 2025.

Who is the general manager of EVHAHN AS?

Espen Vekseth-Hahn is registered as general manager of EVHAHN AS.

Where is EVHAHN AS based?

EVHAHN AS has its business address in Steinkjer.

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.