BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

ZILLICA AS

Org. no. 913318471 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 473,000
Operating profit NOK −24,000
Equity NOK 110,000
Incorporated 2014
Employees 21
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

ZILLICA AS is registered as a limited company in Oslo, Oslo with organisation number 913318471. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2014 and has 21 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selge tjenester og varer innen bygg- og anlegg, renhold, flytting, event, - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 473,000 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 473,000
Operating profit
NOK −24,000
Equity
NOK 110,000
Est. value
NOK 355,000

Financial health · 2024

Liquidity
2.17
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.0%
Very good
Equity as a share of total capital

Who owns ZILLICA AS?

OLE TORJUS PEDERSEN
ZILLICA AS
NOK 473,000 rev. · NOK −24,000 profit

ZILLICA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZILLICA AS

Who owns ZILLICA AS?

OLE TORJUS PEDERSEN is the largest registered owner, with 50.0%.

What is the revenue of ZILLICA AS?

ZILLICA AS had revenue of NOK 473,000 in 2024.

Where is ZILLICA AS based?

ZILLICA 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.