BIZTRAC BETA
Construction of residential and non-residential buildings

J-A TAK OG BYGG AS

Org. no. 930083224 Limited company (AS) Nord-Aurdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 233,000
Equity NOK 1.2m
Incorporated 2022
Share capital NOK 200,000

J-A TAK OG BYGG AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 930083224. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet knyttet til oppføring, restaurering og vedlikehold av bygg og eiendommer, samt omsetning av varer og tjenester og alt som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 233,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 233,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
61.0%
Very good
Equity as a share of total capital

Who owns J-A TAK OG BYGG AS?

ANDRIUS INVEST AS
J-A TAK OG BYGG AS
NOK 6.3m rev. · NOK 233,000 profit

J-A TAK OG BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about J-A TAK OG BYGG AS

Who owns J-A TAK OG BYGG AS?

ANDRIUS INVEST AS is the largest registered owner, with 75.0%.

What is the revenue of J-A TAK OG BYGG AS?

J-A TAK OG BYGG AS had revenue of NOK 6.3m in 2024.

Who is the general manager of J-A TAK OG BYGG AS?

Andrius Kelpsa is registered as general manager of J-A TAK OG BYGG AS.

Where is J-A TAK OG BYGG AS based?

J-A TAK OG BYGG AS has its business address in Fagernes.

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.