BIZTRAC BETA
Computer programming activities

MIGRIS AS

Org. no. 888400532 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK −1.1m
Equity NOK 4.1m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

MIGRIS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 888400532. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av konsulenttjenester og produkter, samt utvikling av teknologi vedrørende leting etter hydrokarboner, og hva som herved står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK −1.1m
Equity
NOK 4.1m
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns MIGRIS AS?

WENCHE KROKSTAD
MIGRIS AS
NOK 4.5m rev. · NOK −1.1m profit

MIGRIS AS has 5 registered shareholders:

All shareholders and roles →

Which companies does MIGRIS AS own?

MIGRIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MIGRIS AS

Who owns MIGRIS AS?

WENCHE KROKSTAD is the largest registered owner, with 45.0%.

What is the revenue of MIGRIS AS?

MIGRIS AS had revenue of NOK 4.5m in 2024.

Who is the general manager of MIGRIS AS?

Øyvind Sylta is registered as general manager of MIGRIS AS.

Where is MIGRIS AS based?

MIGRIS AS has its business address in Trondheim.

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.