BIZTRAC BETA
Construction of residential and non-residential buildings

JBL BYGG AS

Org. no. 912257053 Limited company (AS) Kvænangen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 254,000
Equity NOK 393,000
Incorporated 2013
Share capital NOK 95,000

JBL BYGG AS is registered as a limited company in Kvænangen, Troms with organisation number 912257053. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 95,000, divided into 3160 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg. Selskapet må også ha muligheten til å drive med annen handelsvirksomhet som er det beste for aksjonærene. Kjøp, salg og utleie av eiendom, samt hva som naturlig hører herunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 254,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 254,000
Equity
NOK 393,000
Est. value
NOK 937,000

Financial health · 2024

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

Who owns JBL BYGG AS?

JOACHIM BOBERG LEIRBAKKEN
JBL BYGG AS
NOK 2.1m rev. · NOK 254,000 profit

JBL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JBL BYGG AS

Who owns JBL BYGG AS?

JOACHIM BOBERG LEIRBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of JBL BYGG AS?

JBL BYGG AS had revenue of NOK 2.1m in 2024.

Who is the general manager of JBL BYGG AS?

Joachim Boberg Leirbakken is registered as general manager of JBL BYGG AS.

Where is JBL BYGG AS based?

JBL BYGG AS has its business address in Burfjord.

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.