BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

JBD SERVICE AS

Org. no. 936680712 Limited company (AS) Sula Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 106,000
Operating profit NOK 81,000
Equity NOK 33,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-14.

JBD SERVICE AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 936680712. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og reparasjon av paller og trevirke, samt bygg-, tømrer- og servicearbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 106,000 in revenue and NOK 81,000 in operating profit.

Key figures · 2025

Revenue
NOK 106,000
Operating profit
NOK 81,000
Equity
NOK 33,000
Est. value
NOK 271,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.5%
Weak
Equity as a share of total capital

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

Who owns JBD SERVICE AS?

HUNTER HUB AS
JBD SERVICE AS
NOK 106,000 rev. · NOK 81,000 profit

JBD SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JBD SERVICE AS

Who owns JBD SERVICE AS?

HUNTER HUB AS is the largest registered owner, with 50.0%.

What is the revenue of JBD SERVICE AS?

JBD SERVICE AS had revenue of NOK 106,000 in 2025.

Who is the general manager of JBD SERVICE AS?

Odin Jæger is registered as general manager of JBD SERVICE AS.

Where is JBD SERVICE AS based?

JBD SERVICE AS has its business address in Langevåg.

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.