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

JAM 3 AS

Org. no. 936228275 Limited company (AS) Enebakk Incorporated 2025 Active
Revenue 2025 NOK 130,000
Operating profit NOK 18,000
Equity NOK 44,000
Incorporated 2025
Employees 7
Share capital NOK 30,000

JAM 3 AS is registered as a limited company in Enebakk, Akershus with organisation number 936228275. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30000 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 130,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 130,000
Operating profit
NOK 18,000
Equity
NOK 44,000
Est. value
NOK 76,000

Financial health · 2025

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

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

Who owns JAM 3 AS?

JAM 3 AS
NOK 130,000 rev. · NOK 18,000 profit

JAM 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAM 3 AS

Who owns JAM 3 AS?

Janis Dubrovskis is the largest registered owner, with 100.0%.

What is the revenue of JAM 3 AS?

JAM 3 AS had revenue of NOK 130,000 in 2025.

Who is the general manager of JAM 3 AS?

Janis Dubrovskis is registered as general manager of JAM 3 AS.

Where is JAM 3 AS based?

JAM 3 AS has its business address in Ytre Enebakk.

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.