BIZTRAC BETA
Uoppgitt

1UP HOLDING AS

Org. no. 923050981 Limited company (AS) Heim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK −7,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

1UP HOLDING AS is registered as a limited company in Heim, Trøndelag with organisation number 923050981. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −7,000

Financial health · 2025

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

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

Who owns 1UP HOLDING AS?

MARIUS SÆTHER
1UP HOLDING AS
NOK 0 rev. · NOK −7,000 profit

1UP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does 1UP HOLDING AS own?

1UP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 1UP HOLDING AS

Who owns 1UP HOLDING AS?

MARIUS SÆTHER is the largest registered owner, with 100.0%.

What is the revenue of 1UP HOLDING AS?

1UP HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of 1UP HOLDING AS?

Marius Sæther is registered as general manager of 1UP HOLDING AS.

Where is 1UP HOLDING AS based?

1UP HOLDING AS has its business address in Valsøybotn.

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.