BIZTRAC BETA
Child welfare services

HELLERUD CONSULT AS

Org. no. 934859359 Limited company (AS) Moss Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −108,000
Equity NOK −78,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

HELLERUD CONSULT AS is registered as a limited company in Moss, Østfold with organisation number 934859359. The business is classified under child welfare services (NACE 88.991). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innen barnevern.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −108,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −108,000
Equity
NOK −78,000

Financial health · 2025

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

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

Who owns HELLERUD CONSULT AS?

GRY SAMUELSEN HELLERUD
HELLERUD CONSULT AS
NOK 1.5m rev. · NOK −108,000 profit

HELLERUD CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELLERUD CONSULT AS

Who owns HELLERUD CONSULT AS?

GRY SAMUELSEN HELLERUD is the largest registered owner, with 100.0%.

What is the revenue of HELLERUD CONSULT AS?

HELLERUD CONSULT AS had revenue of NOK 1.5m in 2025.

Who is the general manager of HELLERUD CONSULT AS?

Gry Samuelsen Hellerud is registered as general manager of HELLERUD CONSULT AS.

Where is HELLERUD CONSULT AS based?

HELLERUD CONSULT AS has its business address in Moss.

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.