biztrac. BETA
COMPANY REGISTER PROFILE
936015786 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

JUMABYGG AS

Org. no. 936015786 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 726,000
Operating profit NOK 293,000
Equity NOK 249,000
Incorporated 2025
Share capital NOK 30,000

JUMABYGG AS is registered as a limited company in Oslo, Oslo with organisation number 936015786. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive innen salg av tjenester i bygge bransjen, malerarbeid, oppussing og rehabilitering av bygninger og andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 726,000 in revenue and NOK 293,000 in operating profit.

Key figures · 2025

Revenue
NOK 726,000
Operating profit
NOK 293,000
Equity
NOK 249,000
Est. value
NOK 958,000

Financial health · 2025

Liquidity
2.01
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
35.1%
Good
Equity as a share of total capital

Who owns JUMABYGG AS?

MB "MD RANGA" LT
JUMABYGG AS
NOK 726,000 rev. · NOK 293,000 profit

JUMABYGG AS has 1 registered shareholder:

  • MB "MD RANGA" 100.0%
All shareholders and roles →

Frequently asked questions about JUMABYGG AS

Who owns JUMABYGG AS?

MB "MD RANGA" is the largest registered owner, with 100.0%.

What is the revenue of JUMABYGG AS?

JUMABYGG AS had revenue of NOK 726,000 in 2025.

Who is the general manager of JUMABYGG AS?

Darius Mikalauskas is registered as general manager of JUMABYGG AS.

Where is JUMABYGG AS based?

JUMABYGG 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.