BIZTRAC BETA
COMPANY REGISTER PROFILE
934922611 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

JM SOLID BYGG AS

Org. no. 934922611 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 7,000
Equity NOK 37,000
Incorporated 2025
Share capital NOK 30,000

JM SOLID BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 934922611. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å selge tømrer tjenester til privat og næring for rehabilitering og nybygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 7,000
Equity
NOK 37,000
Est. value
NOK 48,000

Financial health · 2025

Liquidity
7.80
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JM SOLID BYGG AS?

IOULIA IAROCHENKO
JM SOLID BYGG AS
NOK 2.1m rev. · NOK 7,000 profit

JM SOLID BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JM SOLID BYGG AS

Who owns JM SOLID BYGG AS?

IOULIA IAROCHENKO is the largest registered owner, with 100.0%.

What is the revenue of JM SOLID BYGG AS?

JM SOLID BYGG AS had revenue of NOK 2.1m in 2025.

Who is the general manager of JM SOLID BYGG AS?

Ioulia Iarochenko is registered as general manager of JM SOLID BYGG AS.

Where is JM SOLID BYGG AS based?

JM SOLID BYGG AS has its business address in Oslo.

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.