biztrac. BETA
COMPANY REGISTER PROFILE
923171800 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

STKR INVEST AS

Org. no. 923171800 Limited company (AS) Sandnes Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −47,000
Equity NOK 461,000
Incorporated 2019
Share capital NOK 80,000

Signals

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

STKR INVEST AS is registered as a limited company in Sandnes, Rogaland with organisation number 923171800. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2019. Registered share capital is NOK 80,000, divided into 2667 shares. The company's stated purpose is: “Langsiktig investering i aksjer og annet som står i den forbindelse. Kjøp, salg og utleie av egen fast eiendom og annet som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −47,000
▼ −28 %
Equity
NOK 461,000
▲ +88 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
102.02
Very good
Current assets ÷ current liabilities
Profitability
9.1%
Satisfactory
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns STKR INVEST AS?

STKR INVEST AS
NOK 0 rev. · NOK −47,000 profit

STKR INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STKR INVEST AS own?

STKR INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STKR INVEST AS

Who owns STKR INVEST AS?

JT SUPPLY AS is the largest registered owner, with 62.5%.

What is the revenue of STKR INVEST AS?

STKR INVEST AS had revenue of NOK 0 in 2025.

Where is STKR INVEST AS based?

STKR INVEST AS has its business address in Forsand.

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.