BIZTRAC BETA
Legal activities

ADVOKATFIRMAET ROGSTAD AS

Org. no. 813409682 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 78.4m
Operating profit NOK 10.8m
Equity NOK 12.2m
Incorporated 2014
Employees 45
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ADVOKATFIRMAET ROGSTAD AS is registered as a limited company in Oslo, Oslo with organisation number 813409682. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2014 and has 45 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Juridiske tjenester og strategisk rådgivning innenfor de fleste rettsområder med dertil naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 78.4m in revenue and NOK 10.8m in operating profit.

Key figures · 2025

Revenue
NOK 78.4m
Operating profit
NOK 10.8m
Equity
NOK 12.2m
Est. value
NOK 60.0m

Financial health · 2025

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

Who owns ADVOKATFIRMAET ROGSTAD AS?

FORENSIS HOLDING AS
ADVOKATFIRMAET ROGSTAD AS
NOK 78.4m rev. · NOK 10.8m profit

ADVOKATFIRMAET ROGSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET ROGSTAD AS

Who owns ADVOKATFIRMAET ROGSTAD AS?

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

What is the revenue of ADVOKATFIRMAET ROGSTAD AS?

ADVOKATFIRMAET ROGSTAD AS had revenue of NOK 78.4m in 2025.

Where is ADVOKATFIRMAET ROGSTAD AS based?

ADVOKATFIRMAET ROGSTAD 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.