BIZTRAC BETA
Legal activities

NOAF - NORGES ADVOKATFELLESSKAP AS

Org. no. 919318554 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −657,000
Equity NOK 312,000
Incorporated 2017
Share capital NOK 90,000

Signals

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

NOAF - NORGES ADVOKATFELLESSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 919318554. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 90,000, divided into 900 shares. The company's stated purpose is: “Drive advokatvirksomhet og annen virksomhet som har naturlig tilknytning til advokatvirksomheten, herunder eiendomsmegling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −657,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −657,000
Equity
NOK 312,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns NOAF - NORGES ADVOKATFELLESSKAP AS?

KB3 HOLDING AS
NOAF - NORGES ADVOKATFELLESSKAP AS
NOK 1.6m rev. · NOK −657,000 profit

NOAF - NORGES ADVOKATFELLESSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOAF - NORGES ADVOKATFELLESSKAP AS

Who owns NOAF - NORGES ADVOKATFELLESSKAP AS?

KB3 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NOAF - NORGES ADVOKATFELLESSKAP AS?

NOAF - NORGES ADVOKATFELLESSKAP AS had revenue of NOK 1.6m in 2025.

Where is NOAF - NORGES ADVOKATFELLESSKAP AS based?

NOAF - NORGES ADVOKATFELLESSKAP 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.