BIZTRAC BETA
Plumbing installation

GEORG GJERTSEN AS

Org. no. 921133219 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 1.5m
Equity NOK 3.9m
Incorporated 2018
Share capital NOK 150,000

GEORG GJERTSEN AS is registered as a limited company in Bærum, Akershus with organisation number 921133219. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2018. Registered share capital is NOK 150,000, divided into 2000 shares. The company's stated purpose is: “Rørleggerarbeid, investering i selskaper, utvikling av selskaper og andre rådgivningstjenester i forbindelse med investering og utvikling av selskaper. Videre kan det foretas investeringer i fast eiendom samt utøve eierskap i eiendomsselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 1.5m
Equity
NOK 3.9m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns GEORG GJERTSEN AS?

GEORG BEZIER GJERTSEN
GEORG GJERTSEN AS
NOK 7.0m rev. · NOK 1.5m profit

GEORG GJERTSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GEORG GJERTSEN AS own?

GEORG GJERTSEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GEORG GJERTSEN AS

Who owns GEORG GJERTSEN AS?

GEORG BEZIER GJERTSEN is the largest registered owner, with 100.0%.

What is the revenue of GEORG GJERTSEN AS?

GEORG GJERTSEN AS had revenue of NOK 7.0m in 2024.

Where is GEORG GJERTSEN AS based?

GEORG GJERTSEN AS has its business address in Lommedalen.

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.