BIZTRAC BETA
Landscape service activities

UTESERVICE AS

Org. no. 921038844 Limited company (AS) Bjørnafjorden Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 981,000
Operating profit NOK −111,000
Equity NOK −97,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

Signals

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

UTESERVICE AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 921038844. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Alt innen eiendomsservice.”. The most recent filed accounts, for the 2025 financial year, show NOK 981,000 in revenue and NOK −111,000 in operating profit.

Key figures · 2025

Revenue
NOK 981,000
Operating profit
NOK −111,000
Equity
NOK −97,000

Financial health · 2025

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

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

Who owns UTESERVICE AS?

TRYGVE BERENTZEN
UTESERVICE AS
NOK 981,000 rev. · NOK −111,000 profit

UTESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UTESERVICE AS

Who owns UTESERVICE AS?

TRYGVE BERENTZEN is the largest registered owner, with 100.0%.

What is the revenue of UTESERVICE AS?

UTESERVICE AS had revenue of NOK 981,000 in 2025.

Who is the general manager of UTESERVICE AS?

Trygve Berentzen is registered as general manager of UTESERVICE AS.

Where is UTESERVICE AS based?

UTESERVICE AS has its business address in Os.

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.