BIZTRAC BETA
Construction of residential and non-residential buildings

JMM BYGG AS

Org. no. 923239693 Limited company (AS) Alta Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 292,000
Equity NOK 242,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-14 Adresseendring registrert 2026-02-14.

JMM BYGG AS is registered as a limited company in Alta, Finnmark with organisation number 923239693. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rivning, renovering og oppsett av bygg, samt virksomhet som hører naturlig sammen med dette. Produksjon og salg av håndtverksprodukter, investere i andre selskaper, og liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 292,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 292,000
Equity
NOK 242,000
Est. value
NOK 973,000

Financial health · 2025

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

Who owns JMM BYGG AS?

JAN-MAGNE MATHISEN
JMM BYGG AS
NOK 2.0m rev. · NOK 292,000 profit

JMM BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JMM BYGG AS

Who owns JMM BYGG AS?

JAN-MAGNE MATHISEN is the largest registered owner, with 51.0%.

What is the revenue of JMM BYGG AS?

JMM BYGG AS had revenue of NOK 2.0m in 2025.

Who is the general manager of JMM BYGG AS?

Jan-Magne Mathisen is registered as general manager of JMM BYGG AS.

Where is JMM BYGG AS based?

JMM BYGG AS has its business address in Alta.

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.