BIZTRAC BETA
Retail sale of games and toys

PRITEX TEAM AS

Org. no. 914273293 Limited company (AS) Alta Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.6m
Equity NOK 20.1m
Incorporated 2014
Share capital NOK 430,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PRITEX TEAM AS is registered as a limited company in Alta, Finnmark with organisation number 914273293. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2014. Registered share capital is NOK 430,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer, rådgivning, samt annen virksomhet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.6m
Equity
NOK 20.1m
Est. value
NOK 25.1m

Financial health · 2024

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

Who owns PRITEX TEAM AS?

MORTEN EK
PRITEX TEAM AS
NOK 0 rev. · NOK −1.6m profit

PRITEX TEAM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PRITEX TEAM AS own?

PRITEX TEAM AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about PRITEX TEAM AS

Who owns PRITEX TEAM AS?

MORTEN EK is the largest registered owner, with 50.0%.

What is the revenue of PRITEX TEAM AS?

PRITEX TEAM AS had revenue of NOK 0 in 2024.

Where is PRITEX TEAM AS based?

PRITEX TEAM AS has its business address in Alta.

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.