BIZTRAC BETA
Business and other management consultancy activities

HENO AS

Org. no. 989137530 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 21,000
Operating profit NOK −121,000
Equity NOK 225,000
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−121k kr).
  • Nylig endring 2026-07-29 Adresseendring registrert 2026-07-29.

HENO AS is registered as a limited company in Oslo, Oslo with organisation number 989137530. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester for andre og andre produkter/tjenester som naturlig hører sammen med dette, investeringer i verdipapirer, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21,000 in revenue and NOK −121,000 in operating profit.

Key figures · 2024

Revenue
NOK 21,000
Operating profit
NOK −121,000
Equity
NOK 225,000
Est. value
NOK 132,000

Financial health · 2024

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

Who owns HENO AS?

HELGE NORLAND
HENO AS
NOK 21,000 rev. · NOK −121,000 profit

HENO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENO AS

Who owns HENO AS?

HELGE NORLAND is the largest registered owner, with 100.0%.

What is the revenue of HENO AS?

HENO AS had revenue of NOK 21,000 in 2024.

Who is the general manager of HENO AS?

Helge Norland is registered as general manager of HENO AS.

Where is HENO AS based?

HENO 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.