BIZTRAC BETA
COMPANY REGISTER PROFILE
998468027 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

HELSEKNEKKEN AS

Org. no. 998468027 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 12.7m
Incorporated 2012
Share capital NOK 1.0m

Signals

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

HELSEKNEKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 998468027. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Handel, investering i fast eiendom og verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egenkapital. Samt markedsføring, profilering og sponsorvirksomhet som understøtter selskapets investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
▼ −612 %
Equity
NOK 12.7m
▲ +234 %
Est. value
NOK 65.5m

Financial health · 2025

Liquidity
114.33
Very good
Current assets ÷ current liabilities
Profitability
94.3%
Very good
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns HELSEKNEKKEN AS?

HELSEKNEKKEN AS
NOK 0 rev. · NOK −22,000 profit

HELSEKNEKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELSEKNEKKEN AS

Who owns HELSEKNEKKEN AS?

ØISTEIN WIDDING is the largest registered owner, with 100.0%.

What is the revenue of HELSEKNEKKEN AS?

HELSEKNEKKEN AS had revenue of NOK 0 in 2025.

Where is HELSEKNEKKEN AS based?

HELSEKNEKKEN 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 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.