BIZTRAC BETA
Other technical consultancy

SELSITECH AS

Org. no. 925272930 Limited company (AS) Aukra Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 555,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SELSITECH AS is registered as a limited company in Aukra, Møre og Romsdal with organisation number 925272930. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler og alt hva dermed står i forbindelse, samt konsulenttjenester innen olje- og gassvirksomhet.”. 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 555,000
Est. value
NOK 12.4m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.6%
Good
Equity as a share of total capital

Who owns SELSITECH AS?

BJØRNAR SMÅGE
SELSITECH AS
NOK 0 rev. · NOK −7,000 profit

SELSITECH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SELSITECH AS own?

SELSITECH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SELSITECH AS

Who owns SELSITECH AS?

BJØRNAR SMÅGE is the largest registered owner, with 100.0%.

What is the revenue of SELSITECH AS?

SELSITECH AS had revenue of NOK 0 in 2025.

Who is the general manager of SELSITECH AS?

Bjørnar Småge is registered as general manager of SELSITECH AS.

Where is SELSITECH AS based?

SELSITECH AS has its business address in Aukra.

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.