BIZTRAC BETA
Construction of residential and non-residential buildings

JORA BYGG OG LAFT AS

Org. no. 982007496 Limited company (AS) Lesja Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 38.9m
Operating profit NOK 1.6m
Equity NOK 8.7m
Incorporated 2000
Employees 21
Share capital NOK 100,000

JORA BYGG OG LAFT AS is registered as a limited company in Lesja, Innlandet with organisation number 982007496. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2000 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive snekker og laftevirksomhet samt salg av varer og tjenester innenfor denne sektoren, herundr deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 38.9m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 38.9m
Operating profit
NOK 1.6m
Equity
NOK 8.7m
Est. value
NOK 10.0m

Financial health · 2025

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

Who owns JORA BYGG OG LAFT AS?

GEIR GROVEN
JORA BYGG OG LAFT AS
NOK 38.9m rev. · NOK 1.6m profit

JORA BYGG OG LAFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JORA BYGG OG LAFT AS

Who owns JORA BYGG OG LAFT AS?

GEIR GROVEN is the largest registered owner, with 93.0%.

What is the revenue of JORA BYGG OG LAFT AS?

JORA BYGG OG LAFT AS had revenue of NOK 38.9m in 2025.

Who is the general manager of JORA BYGG OG LAFT AS?

Terje Andersen is registered as general manager of JORA BYGG OG LAFT AS.

Where is JORA BYGG OG LAFT AS based?

JORA BYGG OG LAFT AS has its business address in Lesja.

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.