BIZTRAC BETA
Computer consultancy and computer facilities management activities

HOLLI UNITED WORKS AS

Org. no. 919194308 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 148,000
Equity NOK −51,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−51k kr).

HOLLI UNITED WORKS AS is registered as a limited company in Oslo, Oslo with organisation number 919194308. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “IT-konsulenttjenester og -rådgivning. IT-annet, nettløsninger, domeneløsninger og nettsiderådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 148,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 148,000
Equity
NOK −51,000
Est. value
NOK 1.7m

Financial health · 2025

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

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

Who owns HOLLI UNITED WORKS AS?

ARNE BØRRE HOLLI
HOLLI UNITED WORKS AS
NOK 1.1m rev. · NOK 148,000 profit

HOLLI UNITED WORKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLLI UNITED WORKS AS

Who owns HOLLI UNITED WORKS AS?

ARNE BØRRE HOLLI is the largest registered owner, with 100.0%.

What is the revenue of HOLLI UNITED WORKS AS?

HOLLI UNITED WORKS AS had revenue of NOK 1.1m in 2025.

Where is HOLLI UNITED WORKS AS based?

HOLLI UNITED WORKS 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.