biztrac. BETA
COMPANY REGISTER PROFILE
935018757 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ANTIRE EMPLOYEECO AS

Org. no. 935018757 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 10.0m
Incorporated 2025
Share capital NOK 100,000

Signals

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

ANTIRE EMPLOYEECO AS is registered as a limited company in Oslo, Oslo with organisation number 935018757. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 10000000 shares. The company's stated purpose is: “Investere i og eie aksjer og andre finansielle instrumenter eller andeler samt virksomhet som naturlig hører med til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 10.0m
Est. value
NOK 11.7m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
82.2%
Very good
Equity as a share of total capital

Who owns ANTIRE EMPLOYEECO AS?

ANTIRE EMPLOYEECO AS has 20 registered shareholders:

All shareholders and roles →

Which companies does ANTIRE EMPLOYEECO AS own?

ANTIRE EMPLOYEECO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ANTIRE EMPLOYEECO AS

Who owns ANTIRE EMPLOYEECO AS?

PROJECT SCALE TOPCO AS is the largest registered owner, with 79.8%.

What is the revenue of ANTIRE EMPLOYEECO AS?

ANTIRE EMPLOYEECO AS had revenue of NOK 0 in 2025.

Where is ANTIRE EMPLOYEECO AS based?

ANTIRE EMPLOYEECO 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 03.10.2026.

Report a problem

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