BIZTRAC BETA
Office administrative and support activities

DRIFT ADVOKATHJØRNET AS

Org. no. 922114315 Limited company (AS) Lyngdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 599,000
Operating profit NOK −7,000
Equity NOK 54,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

DRIFT ADVOKATHJØRNET AS is registered as a limited company in Lyngdal, Agder with organisation number 922114315. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Leie og drift av kontor for aksjonærenes advokatvirksomhet i kontorfellesskapet Advokathjørnet.”. The most recent filed accounts, for the 2025 financial year, show NOK 599,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 599,000
Operating profit
NOK −7,000
Equity
NOK 54,000
Est. value
NOK 407,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DRIFT ADVOKATHJØRNET AS?

ADVOKATFIRMAET KARLSEN AS
DRIFT ADVOKATHJØRNET AS
NOK 599,000 rev. · NOK −7,000 profit

DRIFT ADVOKATHJØRNET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIFT ADVOKATHJØRNET AS

Who owns DRIFT ADVOKATHJØRNET AS?

ADVOKATFIRMAET KARLSEN AS is the largest registered owner, with 50.0%.

What is the revenue of DRIFT ADVOKATHJØRNET AS?

DRIFT ADVOKATHJØRNET AS had revenue of NOK 599,000 in 2025.

Where is DRIFT ADVOKATHJØRNET AS based?

DRIFT ADVOKATHJØRNET AS has its business address in Lyngdal.

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.