BIZTRAC BETA
Rental and operating of own or leased real estate

GJERTSEN EIENDOM AS

Org. no. 824826072 Limited company (AS) Sandefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 411,000
Operating profit NOK 282,000
Equity NOK 636,000
Incorporated 2020
Share capital NOK 30,000

GJERTSEN EIENDOM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 824826072. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, og drift av eiendom, arbeid innenfor murerfaget, konsulenttjenester og alt hva her naturlig hører innunder samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 411,000 in revenue and NOK 282,000 in operating profit.

Key figures · 2025

Revenue
NOK 411,000
Operating profit
NOK 282,000
Equity
NOK 636,000
Est. value
NOK 976,000

Financial health · 2025

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

Who owns GJERTSEN EIENDOM AS?

GJERTSEN INVEST AS
GJERTSEN EIENDOM AS
NOK 411,000 rev. · NOK 282,000 profit

GJERTSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJERTSEN EIENDOM AS

Who owns GJERTSEN EIENDOM AS?

GJERTSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GJERTSEN EIENDOM AS?

GJERTSEN EIENDOM AS had revenue of NOK 411,000 in 2025.

Who is the general manager of GJERTSEN EIENDOM AS?

Oddbjørn Gjertsen is registered as general manager of GJERTSEN EIENDOM AS.

Where is GJERTSEN EIENDOM AS based?

GJERTSEN EIENDOM AS has its business address in Sandefjord.

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.