BIZTRAC BETA
General medical practice activities

WILHELM GRINI JOHANSEN AS

Org. no. 991440917 Limited company (AS) Ringsaker Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −210,000
Equity NOK 3.7m
Incorporated 2007
Share capital NOK 100,000

Signals

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

WILHELM GRINI JOHANSEN AS is registered as a limited company in Ringsaker, Innlandet with organisation number 991440917. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Legevirksomhet og investeringer i verdipapirer og annen investeringsvirksomhet. Virksomheten kan også utøves gjennom deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −210,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −210,000
Equity
NOK 3.7m
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
13.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.1%
Very good
Equity as a share of total capital

Who owns WILHELM GRINI JOHANSEN AS?

WILHELM GRINI JOHANSEN
WILHELM GRINI JOHANSEN AS
NOK 1.7m rev. · NOK −210,000 profit

WILHELM GRINI JOHANSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WILHELM GRINI JOHANSEN AS

Who owns WILHELM GRINI JOHANSEN AS?

WILHELM GRINI JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of WILHELM GRINI JOHANSEN AS?

WILHELM GRINI JOHANSEN AS had revenue of NOK 1.7m in 2025.

Where is WILHELM GRINI JOHANSEN AS based?

WILHELM GRINI JOHANSEN AS has its business address in Rudshøgda.

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.