biztrac. BETA
COMPANY REGISTER PROFILE
916650701 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

ATILIKA NORGE AS

Org. no. 916650701 Limited company (AS) Horten Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 174,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

ATILIKA NORGE AS is registered as a limited company in Horten, Vestfold with organisation number 916650701. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levere tjenester innen IKT og programvareutvikling, være agent for salg av programvarelisenser, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
▼ −22 %
Equity
NOK 174,000
▼ −11 %
Est. value
NOK 315,000

Financial health · 2025

Liquidity
67.05
Very good
Current assets ÷ current liabilities
Profitability
-11.3%
Not satisfactory
Return on total assets
Solidity
98.5%
Very good
Equity as a share of total capital

Who owns ATILIKA NORGE AS?

ATILIKA INC JP
ATILIKA NORGE AS
NOK 0 rev. · NOK −21,000 profit

ATILIKA NORGE AS has 1 registered shareholder:

  • ATILIKA INC 100.0%
All shareholders and roles →

Frequently asked questions about ATILIKA NORGE AS

Who owns ATILIKA NORGE AS?

ATILIKA INC is the largest registered owner, with 100.0%.

What is the revenue of ATILIKA NORGE AS?

ATILIKA NORGE AS had revenue of NOK 0 in 2025.

Where is ATILIKA NORGE AS based?

ATILIKA NORGE AS has its business address in Horten.

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.