BIZTRAC BETA
Construction of residential and non-residential buildings

JAG BYGG AS

Org. no. 997952235 Limited company (AS) Kvinesdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 404,000
Operating profit NOK 73,000
Equity NOK 86,000
Incorporated 2012
Share capital NOK 30,000

JAG BYGG AS is registered as a limited company in Kvinesdal, Agder with organisation number 997952235. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggentreprenør, herunder oppføring og vedlikehold av bygg, drive handel med byggevarer, og hva dermed står i forbindelse, utleie av egen arbeidskraft samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 404,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2025

Revenue
NOK 404,000
Operating profit
NOK 73,000
Equity
NOK 86,000
Est. value
NOK 257,000

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.3%
Weak
Equity as a share of total capital

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

Who owns JAG BYGG AS?

JAN ARNE GÅSELAND
JAG BYGG AS
NOK 404,000 rev. · NOK 73,000 profit

JAG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAG BYGG AS

Who owns JAG BYGG AS?

JAN ARNE GÅSELAND is the largest registered owner, with 100.0%.

What is the revenue of JAG BYGG AS?

JAG BYGG AS had revenue of NOK 404,000 in 2025.

Who is the general manager of JAG BYGG AS?

Jan Arne Gåseland is registered as general manager of JAG BYGG AS.

Where is JAG BYGG AS based?

JAG BYGG AS has its business address in Kvinesdal.

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.