BIZTRAC BETA
Repair and maintenance of machinery

STECH AS

Org. no. 927362678 Limited company (AS) Jevnaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 144,000
Equity NOK −481,000
Incorporated 2021
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−481k kr).

STECH AS is registered as a limited company in Jevnaker, Akershus with organisation number 927362678. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive tjenesteytende virksomhet innen mekaniske tjenester, handel med kjøretøy og utstyr, samt konsulent- og oppdragsvirksomhet for andre foretak, herunder deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 144,000
Equity
NOK −481,000
Est. value
NOK 729,000

Financial health · 2025

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

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

Who owns STECH AS?

SIMEN SVENSBRÅTEN
STECH AS
NOK 4.5m rev. · NOK 144,000 profit

STECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STECH AS

Who owns STECH AS?

SIMEN SVENSBRÅTEN is the largest registered owner, with 100.0%.

What is the revenue of STECH AS?

STECH AS had revenue of NOK 4.5m in 2025.

Who is the general manager of STECH AS?

Simen Svensbråten is registered as general manager of STECH AS.

Where is STECH AS based?

STECH AS has its business address in Jevnaker.

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.