BIZTRAC BETA
Computer consultancy and computer facilities management activities

ARCTIC BYTE AS

Org. no. 932463857 Limited company (AS) Nesodden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK −403
Operating profit NOK −6,000
Equity NOK 49,000
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

ARCTIC BYTE AS is registered as a limited company in Nesodden, Akershus with organisation number 932463857. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 6000 shares. The company's stated purpose is: “Utvikling av software og investering.”. The most recent filed accounts, for the 2024 financial year, show NOK −403 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK −403
Operating profit
NOK −6,000
Equity
NOK 49,000
Est. value
NOK 89,000

Financial health · 2024

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

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

Who owns ARCTIC BYTE AS?

PETER JAMES SAMUEL
ARCTIC BYTE AS
NOK −403 rev. · NOK −6,000 profit

ARCTIC BYTE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC BYTE AS

Who owns ARCTIC BYTE AS?

PETER JAMES SAMUEL is the largest registered owner, with 25.0%.

What is the revenue of ARCTIC BYTE AS?

ARCTIC BYTE AS had revenue of NOK −403 in 2024.

Who is the general manager of ARCTIC BYTE AS?

Sten Kristian Schiøtz Solseth is registered as general manager of ARCTIC BYTE AS.

Where is ARCTIC BYTE AS based?

ARCTIC BYTE AS has its business address in Nesoddtangen.

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.