BIZTRAC BETA
COMPANY REGISTER PROFILE
861407942 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

GJÆRDAL EIENDOM AS

Org. no. 861407942 Limited company (AS) Larvik Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 908,000
Equity NOK 11.5m
Incorporated 1991
Share capital NOK 899,000

GJÆRDAL EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 861407942. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1991. Registered share capital is NOK 899,000, divided into 2900 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, og det som står i forbindelse med dette, samt eie og forvalte aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 908,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 908,000
Equity
NOK 11.5m
Est. value
NOK 10.6m

Financial health · 2025

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

Who owns GJÆRDAL EIENDOM AS?

GJÆRDAL EIENDOM AS
NOK 1.6m rev. · NOK 908,000 profit

GJÆRDAL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJÆRDAL EIENDOM AS

Who owns GJÆRDAL EIENDOM AS?

LIV SOLVEIG ALLUM is the largest registered owner, with 100.0%.

What is the revenue of GJÆRDAL EIENDOM AS?

GJÆRDAL EIENDOM AS had revenue of NOK 1.6m in 2025.

Who is the general manager of GJÆRDAL EIENDOM AS?

Ove Hansen is registered as general manager of GJÆRDAL EIENDOM AS.

Where is GJÆRDAL EIENDOM AS based?

GJÆRDAL EIENDOM AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.