BIZTRAC BETA
Computer programming activities

SENSETEQ AS

Org. no. 924581662 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 750,000
Operating profit NOK −1.6m
Equity NOK −4.6m
Incorporated 2020
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

SENSETEQ AS is registered as a limited company in Bergen, Vestland with organisation number 924581662. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 1.0m, divided into 30000 shares. The company's stated purpose is: “Bistå i rekruttering av teknisk personale for kortsiktige og langsiktige oppdrag - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 750,000 in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 750,000
Operating profit
NOK −1.6m
Equity
NOK −4.6m

Financial health · 2024

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

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

Who owns SENSETEQ AS?

FOI HOLDING AS
SENSETEQ AS
NOK 750,000 rev. · NOK −1.6m profit

SENSETEQ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SENSETEQ AS

Who owns SENSETEQ AS?

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

What is the revenue of SENSETEQ AS?

SENSETEQ AS had revenue of NOK 750,000 in 2024.

Where is SENSETEQ AS based?

SENSETEQ AS has its business address in Bergen.

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.