BIZTRAC BETA
Repair and maintenance of consumer electronics

YAAY AS

Org. no. 934294807 Limited company (AS) Indre Østfold Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −25,000
Equity NOK −11,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

YAAY AS is registered as a limited company in Indre Østfold, Østfold with organisation number 934294807. The business is classified under repair and maintenance of consumer electronics (NACE 95.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tjenester innen IT/media, reparasjon av elektriske og elektroniske artikler, produksjon av møbler.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −25,000
Equity
NOK −11,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3263.3%
Weak
Equity as a share of total capital

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

Who owns YAAY AS?

Viktor Fagerheim
YAAY AS
NOK 4,000 rev. · NOK −25,000 profit

YAAY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about YAAY AS

Who owns YAAY AS?

Viktor Fagerheim is the largest registered owner, with 33.3%.

What is the revenue of YAAY AS?

YAAY AS had revenue of NOK 4,000 in 2025.

Who is the general manager of YAAY AS?

Yngve Stavnes Fagerheim is registered as general manager of YAAY AS.

Where is YAAY AS based?

YAAY AS has its business address in Mysen.

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.