BIZTRAC BETA
Rental and operating of own or leased real estate

GJERDEN INVEST AS

Org. no. 995051818 Limited company (AS) Larvik Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 527,000
Equity NOK 15.3m
Incorporated 2009
Share capital NOK 100,000

GJERDEN INVEST AS is registered as a limited company in Larvik, Vestfold with organisation number 995051818. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester samt investeringer i andre foretak, herunder fast eiendom”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 527,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 527,000
Equity
NOK 15.3m
Est. value
NOK 11.5m

Financial health · 2024

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

Who owns GJERDEN INVEST AS?

VEGAR GJERDEN
GJERDEN INVEST AS
NOK 2.3m rev. · NOK 527,000 profit

GJERDEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GJERDEN INVEST AS own?

GJERDEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GJERDEN INVEST AS

Who owns GJERDEN INVEST AS?

VEGAR GJERDEN is the largest registered owner, with 80.0%.

What is the revenue of GJERDEN INVEST AS?

GJERDEN INVEST AS had revenue of NOK 2.3m in 2024.

Who is the general manager of GJERDEN INVEST AS?

Vegar Gjerden is registered as general manager of GJERDEN INVEST AS.

Where is GJERDEN INVEST AS based?

GJERDEN INVEST AS has its business address in Svarstad.

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.