BIZTRAC BETA
Wholesale of machine tools

SLIP & SPESIALVERKTØY AS

Org. no. 994271296 Limited company (AS) Time Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK −114,000
Equity NOK 514,000
Incorporated 2009
Share capital NOK 101,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−114k kr).

SLIP & SPESIALVERKTØY AS is registered as a limited company in Time, Rogaland with organisation number 994271296. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 2009. Registered share capital is NOK 101,000, divided into 504 shares. The company's stated purpose is: “Handel, produksjon og servicearbeid, samt deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK −114,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK −114,000
Equity
NOK 514,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.9%
Very good
Equity as a share of total capital

Who owns SLIP & SPESIALVERKTØY AS?

ING YNGVE EGE AS
SLIP & SPESIALVERKTØY AS
NOK 4.1m rev. · NOK −114,000 profit

SLIP & SPESIALVERKTØY AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLIP & SPESIALVERKTØY AS

Who owns SLIP & SPESIALVERKTØY AS?

ING YNGVE EGE AS is the largest registered owner, with 28.6%.

What is the revenue of SLIP & SPESIALVERKTØY AS?

SLIP & SPESIALVERKTØY AS had revenue of NOK 4.1m in 2024.

Who is the general manager of SLIP & SPESIALVERKTØY AS?

Øystein Sande Johnsen is registered as general manager of SLIP & SPESIALVERKTØY AS.

Where is SLIP & SPESIALVERKTØY AS based?

SLIP & SPESIALVERKTØY AS has its business address in Bryne.

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.