BIZTRAC BETA
Wholesale of other food

TUPLE AS

Org. no. 931423053 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4,000
Operating profit NOK −7,000
Equity NOK 12,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).
  • Nylig endring 2026-06-14 Adresseendring registrert 2026-06-14.

TUPLE AS is registered as a limited company in Oslo, Oslo with organisation number 931423053. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling, drift og markedsføring av digitale tjenester og nettbaserte handelsløsninger, inkludert nettbutikk, design, programvareutvikling, innholdsproduksjon og rådgivning innen digital markedsføring. Selskapet kan også drive relaterte aktiviteter og investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 4,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 4,000
Operating profit
NOK −7,000
Equity
NOK 12,000
Est. value
NOK 7,000

Financial health · 2024

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

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

Who owns TUPLE AS?

FAUZI FARISS
TUPLE AS
NOK 4,000 rev. · NOK −7,000 profit

TUPLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUPLE AS

Who owns TUPLE AS?

FAUZI FARISS is the largest registered owner, with 100.0%.

What is the revenue of TUPLE AS?

TUPLE AS had revenue of NOK 4,000 in 2024.

Where is TUPLE AS based?

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