BIZTRAC BETA
Business and other management consultancy activities

SEHU CONSULTING AS

Org. no. 934958985 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

SEHU CONSULTING AS is registered as a limited company in Drammen, Buskerud with organisation number 934958985. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet, rådgivning og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

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

Who owns SEHU CONSULTING AS?

STEFFEN HAUG
SEHU CONSULTING AS
NOK 1.1m rev. · NOK −6,000 profit

SEHU CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEHU CONSULTING AS

Who owns SEHU CONSULTING AS?

STEFFEN HAUG is the largest registered owner, with 100.0%.

What is the revenue of SEHU CONSULTING AS?

SEHU CONSULTING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SEHU CONSULTING AS?

Steffen Haug is registered as general manager of SEHU CONSULTING AS.

Where is SEHU CONSULTING AS based?

SEHU CONSULTING AS has its business address in Svelvik.

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.