BIZTRAC BETA
Legal activities

ADVOKATKONTORET MYHR & CO AS

Org. no. 918824898 Limited company (AS) Melhus Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 2.2m
Equity NOK 814,000
Incorporated 2017
Share capital NOK 100,000

ADVOKATKONTORET MYHR & CO AS is registered as a limited company in Melhus, Trøndelag with organisation number 918824898. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Advokatvirksomhet, juridiske tjenester og generelle konsulenttjenester, samt andre tiltak beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 12.5m
Operating profit
NOK 2.2m
Equity
NOK 814,000
Est. value
NOK 10.5m

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.6%
Weak
Equity as a share of total capital

Who owns ADVOKATKONTORET MYHR & CO AS?

VALÅS MYHR HOLDING AS
ADVOKATKONTORET MYHR & CO AS
NOK 12.5m rev. · NOK 2.2m profit

ADVOKATKONTORET MYHR & CO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATKONTORET MYHR & CO AS

Who owns ADVOKATKONTORET MYHR & CO AS?

VALÅS MYHR HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of ADVOKATKONTORET MYHR & CO AS?

ADVOKATKONTORET MYHR & CO AS had revenue of NOK 12.5m in 2025.

Who is the general manager of ADVOKATKONTORET MYHR & CO AS?

Mia Ingebrigtsen is registered as general manager of ADVOKATKONTORET MYHR & CO AS.

Where is ADVOKATKONTORET MYHR & CO AS based?

ADVOKATKONTORET MYHR & CO AS has its business address in Melhus.

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.