BIZTRAC BETA
Site preparation

SILSAND MASKIN AS

Org. no. 974520737 Limited company (AS) Senja Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 60.1m
Operating profit NOK 4.8m
Equity NOK 16.4m
Incorporated 1995
Employees 23
Share capital NOK 100,000

SILSAND MASKIN AS is registered as a limited company in Senja, Troms with organisation number 974520737. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1995 and has 23 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinstasjon samt hva hermed står i forbindelse, samt ved aksjetegning eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 60.1m in revenue and NOK 4.8m in operating profit.

Key figures · 2024

Revenue
NOK 60.1m
Operating profit
NOK 4.8m
Equity
NOK 16.4m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns SILSAND MASKIN AS?

KATO JOHANSEN
SILSAND MASKIN AS
NOK 60.1m rev. · NOK 4.8m profit

SILSAND MASKIN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SILSAND MASKIN AS own?

SILSAND MASKIN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SILSAND MASKIN AS

Who owns SILSAND MASKIN AS?

KATO JOHANSEN is the largest registered owner, with 33.0%.

What is the revenue of SILSAND MASKIN AS?

SILSAND MASKIN AS had revenue of NOK 60.1m in 2024.

Who is the general manager of SILSAND MASKIN AS?

Kato Johansen is registered as general manager of SILSAND MASKIN AS.

Where is SILSAND MASKIN AS based?

SILSAND MASKIN AS has its business address in Silsand.

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.