biztrac. BETA
COMPANY REGISTER PROFILE
984071329 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Legal activities

ADVOKATFIRMAET RØED AS

Org. no. 984071329 Limited company (AS) Larvik Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 845,000
Equity NOK 1.2m
Incorporated 2001
Share capital NOK 100,000

ADVOKATFIRMAET RØED AS is registered as a limited company in Larvik, Vestfold with organisation number 984071329. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Advokatvirksomhet og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 845,000 in operating profit.

Former names: ADVOKATFIRMAET OLE TOM RØED AS

Key figures · 2025

Revenue
NOK 2.9m
▲ +22 %
Operating profit
NOK 845,000
▲ +39 %
Equity
NOK 1.2m
▲ +33 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
3.02
Very good
Current assets ÷ current liabilities
Profitability
47.4%
Very good
Return on total assets
Solidity
66.0%
Very good
Equity as a share of total capital

Who owns ADVOKATFIRMAET RØED AS?

ADVOKATFIRMAET RØED AS
NOK 2.9m rev. · NOK 845,000 profit

ADVOKATFIRMAET RØED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET RØED AS

Who owns ADVOKATFIRMAET RØED AS?

Øyvind Røed is the largest registered owner, with 100.0%.

What is the revenue of ADVOKATFIRMAET RØED AS?

ADVOKATFIRMAET RØED AS had revenue of NOK 2.9m in 2025.

Who is the general manager of ADVOKATFIRMAET RØED AS?

Øyvind Røed is registered as general manager of ADVOKATFIRMAET RØED AS.

Where is ADVOKATFIRMAET RØED AS based?

ADVOKATFIRMAET RØED AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.