biztrac. BETA
COMPANY REGISTER PROFILE
935478499 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

SYMETRISK AS

Org. no. 935478499 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 734,000
Operating profit NOK −2.0m
Equity NOK 19,000
Incorporated 2025
Share capital NOK 2.2m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).
  • Nylig endring 2026-09-23 Aksjekapital registrert 2026-09-23.

SYMETRISK AS is registered as a limited company in Oslo, Oslo with organisation number 935478499. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 2.2m, divided into 2160000 shares. The company's stated purpose is: “IT-utvikling og salg av utviklede tjenester/produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 734,000 in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 734,000
Operating profit
NOK −2.0m
Equity
NOK 19,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.1%
Weak
Equity as a share of total capital

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

Who owns SYMETRISK AS?

SYMETRISK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYMETRISK AS

Who owns SYMETRISK AS?

AWESOME HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of SYMETRISK AS?

SYMETRISK AS had revenue of NOK 734,000 in 2025.

Who is the general manager of SYMETRISK AS?

Ole Christian Eid is registered as general manager of SYMETRISK AS.

Where is SYMETRISK AS based?

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