BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

AUGELEGE INGUNN STØFRING AS

Org. no. 928191788 Limited company (AS) Sunnfjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 1.8m
Equity NOK 4.5m
Incorporated 2021
Share capital NOK 100,000

AUGELEGE INGUNN STØFRING AS is registered as a limited company in Sunnfjord, Vestland with organisation number 928191788. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive augelegeklinikk, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 1.8m
Equity
NOK 4.5m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns AUGELEGE INGUNN STØFRING AS?

ISMAN HOLDING AS
AUGELEGE INGUNN STØFRING AS
NOK 6.7m rev. · NOK 1.8m profit

AUGELEGE INGUNN STØFRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUGELEGE INGUNN STØFRING AS

Who owns AUGELEGE INGUNN STØFRING AS?

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

What is the revenue of AUGELEGE INGUNN STØFRING AS?

AUGELEGE INGUNN STØFRING AS had revenue of NOK 6.7m in 2025.

Who is the general manager of AUGELEGE INGUNN STØFRING AS?

Ingunn Støfring is registered as general manager of AUGELEGE INGUNN STØFRING AS.

Where is AUGELEGE INGUNN STØFRING AS based?

AUGELEGE INGUNN STØFRING AS has its business address in Førde.

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.