BIZTRAC BETA
Rental and operating of own or leased real estate

PROGAR UTVIKLING AS

Org. no. 927458128 Limited company (AS) Søndre Land Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 7.8m
Operating profit NOK 5.4m
Equity NOK 8.4m
Incorporated 2021
Share capital NOK 891,000

PROGAR UTVIKLING AS is registered as a limited company in Søndre Land, Innlandet with organisation number 927458128. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 891,000, divided into 990 shares. The company's stated purpose is: “Å eie og drive fast eiendom i landbruket, maskinutleie i landbruket, samt eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.8m in revenue and NOK 5.4m in operating profit.

Key figures · 2024

Revenue
NOK 7.8m
Operating profit
NOK 5.4m
Equity
NOK 8.4m
Est. value
NOK 17.1m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.4%
Very good
Equity as a share of total capital

Who owns PROGAR UTVIKLING AS?

PROGAR HOLDING AS
PROGAR UTVIKLING AS
NOK 7.8m rev. · NOK 5.4m profit

PROGAR UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Group structure

PROGAR UTVIKLING AS er morselskap for 7 datterselskaper:

Frequently asked questions about PROGAR UTVIKLING AS

Who owns PROGAR UTVIKLING AS?

PROGAR HOLDING AS is the largest registered owner, with 90.4%.

What is the revenue of PROGAR UTVIKLING AS?

PROGAR UTVIKLING AS had revenue of NOK 7.8m in 2024.

Who is the general manager of PROGAR UTVIKLING AS?

Jørgen Karlsen is registered as general manager of PROGAR UTVIKLING AS.

Where is PROGAR UTVIKLING AS based?

PROGAR UTVIKLING AS has its business address in Fall.

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.