biztrac. BETA
COMPANY REGISTER PROFILE
926350161 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of specialist physicians, other than psychiatrists

GRY WARSLA AS

Org. no. 926350161 Limited company (AS) Oslo Incorporated 2020 Active
Revenue 2025 NOK 7.0m
Operating profit NOK 680,000
Equity NOK 948,000
Incorporated 2020
Share capital NOK 30,000

GRY WARSLA AS is registered as a limited company in Oslo, Oslo with organisation number 926350161. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Spesialisert helsetjeneste innen kvinnesykdommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 680,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
▲ +15 %
Operating profit
NOK 680,000
▲ +12 %
Equity
NOK 948,000
▼ −42 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
21.5%
Very good
Return on total assets
Solidity
29.4%
Good
Equity as a share of total capital

Who owns GRY WARSLA AS?

GRY WARSLA AS
NOK 7.0m rev. · NOK 680,000 profit

GRY WARSLA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRY WARSLA AS own?

GRY WARSLA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRY WARSLA AS

Who owns GRY WARSLA AS?

Gry Warsla is the largest registered owner, with 100.0%.

What is the revenue of GRY WARSLA AS?

GRY WARSLA AS had revenue of NOK 7.0m in 2025.

Who is the general manager of GRY WARSLA AS?

Gry Warsla is registered as general manager of GRY WARSLA AS.

Where is GRY WARSLA AS based?

GRY WARSLA 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 03.10.2026.

Report a problem

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