BIZTRAC BETA
Legal activities

ADVOKATFIRMAET JOHNSRUD & CO AS

Org. no. 985223122 Limited company (AS) Hamar Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 15.0m
Operating profit NOK 98,000
Equity NOK 2.0m
Incorporated 2002
Employees 10
Share capital NOK 1.4m

ADVOKATFIRMAET JOHNSRUD & CO AS is registered as a limited company in Hamar, Innlandet with organisation number 985223122. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2002 and has 10 registered employees. Registered share capital is NOK 1.4m, divided into 14400 shares. The company's stated purpose is: “Advokatvirksomhet og hva dermed står i forbindelse”. The most recent filed accounts, for the 2025 financial year, show NOK 15.0m in revenue and NOK 98,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.0m
Operating profit
NOK 98,000
Equity
NOK 2.0m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns ADVOKATFIRMAET JOHNSRUD & CO AS?

STEIN HERVIK
ADVOKATFIRMAET JOHNSRUD & CO AS
NOK 15.0m rev. · NOK 98,000 profit

ADVOKATFIRMAET JOHNSRUD & CO AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET JOHNSRUD & CO AS

Who owns ADVOKATFIRMAET JOHNSRUD & CO AS?

STEIN HERVIK is the largest registered owner, with 16.7%.

What is the revenue of ADVOKATFIRMAET JOHNSRUD & CO AS?

ADVOKATFIRMAET JOHNSRUD & CO AS had revenue of NOK 15.0m in 2025.

Who is the general manager of ADVOKATFIRMAET JOHNSRUD & CO AS?

Åsmund Sørby Foshaug is registered as general manager of ADVOKATFIRMAET JOHNSRUD & CO AS.

Where is ADVOKATFIRMAET JOHNSRUD & CO AS based?

ADVOKATFIRMAET JOHNSRUD & CO AS has its business address in Hamar.

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.