BIZTRAC BETA
Computer programming activities

HEYCIRC AS

Org. no. 935173884 Limited company (AS) Asker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 3,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).

HEYCIRC AS is registered as a limited company in Asker, Akershus with organisation number 935173884. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 3,000
Est. value
NOK 5,000

Financial health · 2025

Liquidity
Not available
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 HEYCIRC AS?

SENTIENT FUTURES HOLDING AS
HEYCIRC AS
NOK 0 rev. · NOK −20,000 profit

HEYCIRC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEYCIRC AS

Who owns HEYCIRC AS?

SENTIENT FUTURES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HEYCIRC AS?

HEYCIRC AS had revenue of NOK 0 in 2025.

Who is the general manager of HEYCIRC AS?

Martin Andreas Olsson Toft is registered as general manager of HEYCIRC AS.

Where is HEYCIRC AS based?

HEYCIRC AS has its business address in Asker.

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.