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

STINSENMAN NORGE AS

Org. no. 921787871 Limited company (AS) Rælingen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 477,000
Equity NOK 437,000
Incorporated 2018
Share capital NOK 30,000

STINSENMAN NORGE AS is registered as a limited company in Rælingen, Akershus with organisation number 921787871. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bearbeiding av metall som f.eks. sveising, montering, boring, overtrekking mv som vanligvis utføres på oppdrags- eller kontraktsbasis.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 477,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
▲ +8 %
Operating profit
NOK 477,000
▲ +2276 %
Equity
NOK 437,000
▲ +544 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
55.8%
Very good
Return on total assets
Solidity
26.6%
Good
Equity as a share of total capital

Who owns STINSENMAN NORGE AS?

STINSENMAN NORGE AS
NOK 6.0m rev. · NOK 477,000 profit

STINSENMAN NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STINSENMAN NORGE AS

Who owns STINSENMAN NORGE AS?

Ilja Arhipov is the largest registered owner, with 100.0%.

What is the revenue of STINSENMAN NORGE AS?

STINSENMAN NORGE AS had revenue of NOK 6.0m in 2025.

Who is the general manager of STINSENMAN NORGE AS?

Ilja Arhipov is registered as general manager of STINSENMAN NORGE AS.

Where is STINSENMAN NORGE AS based?

STINSENMAN NORGE AS has its business address in Løvenstad.

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.