biztrac. BETA
COMPANY REGISTER PROFILE
933145689 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

UTEHJELPEN AS

Org. no. 933145689 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −141,000
Equity NOK 172,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

UTEHJELPEN AS is registered as a limited company in Bærum, Akershus with organisation number 933145689. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Maskinentrepenør, vaktmestertjenester, maskinutleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −141,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▼ −13 %
Operating profit
NOK −141,000
▼ −141 %
Equity
NOK 172,000
▼ −41 %
Est. value
NOK 228,000

Financial health · 2025

Liquidity
3.37
Very good
Current assets ÷ current liabilities
Profitability
-7.7%
Not satisfactory
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns UTEHJELPEN AS?

UTEHJELPEN AS
NOK 2.2m rev. · NOK −141,000 profit

UTEHJELPEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

UTEHJELPEN AS er morselskap for 1 datterselskap:

Frequently asked questions about UTEHJELPEN AS

Who owns UTEHJELPEN AS?

EFR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of UTEHJELPEN AS?

UTEHJELPEN AS had revenue of NOK 2.2m in 2025.

Who is the general manager of UTEHJELPEN AS?

Erik Friis Røkholt is registered as general manager of UTEHJELPEN AS.

Where is UTEHJELPEN AS based?

UTEHJELPEN AS has its business address in Rykkinn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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