biztrac. BETA
COMPANY REGISTER PROFILE
998894654 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Machining of metals

SLIPEHUSET AS

Org. no. 998894654 Limited company (AS) Steinkjer Incorporated 2012 Active
Revenue 2025 NOK 3.0m
Operating profit NOK −427,000
Equity NOK 2.7m
Incorporated 2012
Share capital NOK 290,000

Signals

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

SLIPEHUSET AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 998894654. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2012. Registered share capital is NOK 290,000, divided into 2903450 shares. The company's stated purpose is: “Sliping av redskaper, produksjon, utvikling og salg av tilhørende produkter og tjenester, samt virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK −427,000 in operating profit.

Former names: KNIVSERVICE AS

Key figures · 2025

Revenue
NOK 3.0m
▲ +41 %
Operating profit
NOK −427,000
▼ −204 %
Equity
NOK 2.7m
▲ +429 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
6.17
Very good
Current assets ÷ current liabilities
Profitability
-20.7%
Not satisfactory
Return on total assets
Solidity
87.9%
Very good
Equity as a share of total capital

Who owns SLIPEHUSET AS?

SLIPEHUSET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLIPEHUSET AS

Who owns SLIPEHUSET AS?

Bjørn Mathisen is the largest registered owner, with 46.2%.

What is the revenue of SLIPEHUSET AS?

SLIPEHUSET AS had revenue of NOK 3.0m in 2025.

Who is the general manager of SLIPEHUSET AS?

Martine Haugen is registered as general manager of SLIPEHUSET AS.

Where is SLIPEHUSET AS based?

SLIPEHUSET AS has its business address in Steinkjer.

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.