biztrac. BETA
COMPANY REGISTER PROFILE
930072532 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠ØYVIND AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Temporary employment agency activities and other human resource provisions

ØYVIND AS

Org. no. 930072532 Limited company (AS) Meråker Incorporated 2022 In liquidation
Revenue 2025 NOK 5,000
Operating profit NOK −49,000
Equity NOK 90,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

ØYVIND AS is registered as a limited company in Meråker, Trøndelag with organisation number 930072532. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av tjenester, investering i og utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −49,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
▼ −70 %
Operating profit
NOK −49,000
▼ −915 %
Equity
NOK 90,000
▼ −36 %

Financial health · 2025

Liquidity
4.75
Very good
Current assets ÷ current liabilities
Profitability
-37.5%
Not satisfactory
Return on total assets
Solidity
78.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØYVIND AS?

ØYVIND AS
NOK 5,000 rev. · NOK −49,000 profit

ØYVIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYVIND AS

Who owns ØYVIND AS?

Øyvind Slungård is the largest registered owner, with 100.0%.

What is the revenue of ØYVIND AS?

ØYVIND AS had revenue of NOK 5,000 in 2025.

Where is ØYVIND AS based?

ØYVIND AS has its business address in Meråker.

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.