BIZTRAC BETA
Rental and operating of own or leased real estate

JÅBEKK INDUSTRIBYGG AS

Org. no. 983079660 Limited company (AS) Lindesnes Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.7m
Equity NOK 8.6m
Incorporated 2001
Share capital NOK 2.0m

JÅBEKK INDUSTRIBYGG AS is registered as a limited company in Lindesnes, Agder with organisation number 983079660. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Handel, erverv og drift av eiendommer samt alt hva hermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.7m
Equity
NOK 8.6m
Est. value
NOK 8.6m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.3%
Good
Equity as a share of total capital

Who owns JÅBEKK INDUSTRIBYGG AS?

TOYA AS
JÅBEKK INDUSTRIBYGG AS
NOK 2.3m rev. · NOK 1.7m profit

JÅBEKK INDUSTRIBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JÅBEKK INDUSTRIBYGG AS

Who owns JÅBEKK INDUSTRIBYGG AS?

TOYA AS is the largest registered owner, with 100.0%.

What is the revenue of JÅBEKK INDUSTRIBYGG AS?

JÅBEKK INDUSTRIBYGG AS had revenue of NOK 2.3m in 2024.

Who is the general manager of JÅBEKK INDUSTRIBYGG AS?

Alf Arne Nøsted is registered as general manager of JÅBEKK INDUSTRIBYGG AS.

Where is JÅBEKK INDUSTRIBYGG AS based?

JÅBEKK INDUSTRIBYGG AS has its business address in Mandal.

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.