biztrac. BETA
COMPANY REGISTER PROFILE
932332787 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

JMI BYGGTEAM AS

Org. no. 932332787 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

JMI BYGGTEAM AS is registered as a limited company in Drammen, Buskerud with organisation number 932332787. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Selge varer og tjenester innen snekkerarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: AFAS 131023-19 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
▲ +200 %
Est. value
NOK 31,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns JMI BYGGTEAM AS?

JMI BYGGTEAM AS
NOK 0 rev. · NOK 0 profit

JMI BYGGTEAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JMI BYGGTEAM AS

Who owns JMI BYGGTEAM AS?

Jamshid Marwan Ibrahim is the largest registered owner, with 100.0%.

What is the revenue of JMI BYGGTEAM AS?

JMI BYGGTEAM AS had revenue of NOK 0 in 2025.

Where is JMI BYGGTEAM AS based?

JMI BYGGTEAM AS has its business address in Drammen.

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.