biztrac. BETA
COMPANY REGISTER PROFILE
934304381 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of other civilian transport equipment

IM SOLUTIONS AS

Org. no. 934304381 Limited company (AS) Sola Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 17.5m
Operating profit NOK 31,000
Equity NOK 129,000
Incorporated 2024
Employees 36
Share capital NOK 30,000

IM SOLUTIONS AS is registered as a limited company in Sola, Rogaland with organisation number 934304381. The business is classified under repair and maintenance of other civilian transport equipment (NACE 33.170). The company was incorporated in 2024 and has 36 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Tilby tjenester innen mikromobilitet og 3PL.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.5m in revenue and NOK 31,000 in operating profit.

Former names: AFAS 041024-08 AS

Key figures · 2025

Revenue
NOK 17.5m
▲ +1695 %
Operating profit
NOK 31,000
▼ −84 %
Equity
NOK 129,000
▼ −29 %
Est. value
NOK 329,000

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
1.2%
Weak
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

Who owns IM SOLUTIONS AS?

IM SOLUTIONS AS
NOK 17.5m rev. · NOK 31,000 profit

IM SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IM SOLUTIONS AS

Who owns IM SOLUTIONS AS?

Ivan Melnykovych is the largest registered owner, with 100.0%.

What is the revenue of IM SOLUTIONS AS?

IM SOLUTIONS AS had revenue of NOK 17.5m in 2025.

Who is the general manager of IM SOLUTIONS AS?

Ivan Melnykovych is registered as general manager of IM SOLUTIONS AS.

Where is IM SOLUTIONS AS based?

IM SOLUTIONS AS has its business address in Stavanger.

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.