BIZTRAC BETA
Other real estate activities on a fee or contract basis

J VARHAUG AS

Org. no. 963000561 Limited company (AS) Gjesdal Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 612,000
Operating profit NOK 493,000
Equity NOK 34.5m
Incorporated 1991
Share capital NOK 100,000

J VARHAUG AS is registered as a limited company in Gjesdal, Rogaland with organisation number 963000561. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Forvalte eiendom og andre driftsmidler samt å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 612,000 in revenue and NOK 493,000 in operating profit.

Key figures · 2025

Revenue
NOK 612,000
Operating profit
NOK 493,000
Equity
NOK 34.5m
Est. value
NOK 24.9m

Financial health · 2025

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

Who owns J VARHAUG AS?

JARDAR VARHAUG
J VARHAUG AS
NOK 612,000 rev. · NOK 493,000 profit

J VARHAUG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J VARHAUG AS own?

J VARHAUG AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

J VARHAUG AS er morselskap for 3 datterselskaper:

Frequently asked questions about J VARHAUG AS

Who owns J VARHAUG AS?

JARDAR VARHAUG is the largest registered owner, with 100.0%.

What is the revenue of J VARHAUG AS?

J VARHAUG AS had revenue of NOK 612,000 in 2025.

Who is the general manager of J VARHAUG AS?

Jardar Varhaug is registered as general manager of J VARHAUG AS.

Where is J VARHAUG AS based?

J VARHAUG AS has its business address in Ålgård.

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.