BIZTRAC BETA
Legal activities

ADVOKATFIRMAET GJESSING AS

Org. no. 922393702 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 26.6m
Operating profit NOK 8.4m
Equity NOK 7.5m
Incorporated 2019
Employees 16
Share capital NOK 1.4m

Signals

1 flags
  • Nylig endring 2026-02-20 Aksjekapital registrert 2026-02-20.

ADVOKATFIRMAET GJESSING AS is registered as a limited company in Oslo, Oslo with organisation number 922393702. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2019 and has 16 registered employees. Registered share capital is NOK 1.4m, divided into 70 shares. The company's stated purpose is: “Advokatvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.6m in revenue and NOK 8.4m in operating profit.

Key figures · 2025

Revenue
NOK 26.6m
Operating profit
NOK 8.4m
Equity
NOK 7.5m
Est. value
NOK 31.8m

Financial health · 2025

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

Who owns ADVOKATFIRMAET GJESSING AS?

ADVOKATFIRMAET GJESSING AS
ADVOKATFIRMAET GJESSING AS
NOK 26.6m rev. · NOK 8.4m profit

ADVOKATFIRMAET GJESSING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does ADVOKATFIRMAET GJESSING AS own?

ADVOKATFIRMAET GJESSING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ADVOKATFIRMAET GJESSING AS

Who owns ADVOKATFIRMAET GJESSING AS?

ADVOKATFIRMAET GJESSING AS is the largest registered owner, with 20.6%.

What is the revenue of ADVOKATFIRMAET GJESSING AS?

ADVOKATFIRMAET GJESSING AS had revenue of NOK 26.6m in 2025.

Where is ADVOKATFIRMAET GJESSING AS based?

ADVOKATFIRMAET GJESSING AS has its business address in Oslo.

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.