BIZTRAC BETA
Computer consultancy and computer facilities management activities

YOTDYRIN CONSULTING AS

Org. no. 998601584 Limited company (AS) Drammen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −44,000
Equity NOK 7.8m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−44k kr).

YOTDYRIN CONSULTING AS is registered as a limited company in Drammen, Buskerud with organisation number 998601584. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet, investering i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −44,000
Equity
NOK 7.8m
Est. value
NOK 5.5m

Financial health · 2025

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

Who owns YOTDYRIN CONSULTING AS?

TORSTEIN THUN
YOTDYRIN CONSULTING AS
NOK 0 rev. · NOK −44,000 profit

YOTDYRIN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YOTDYRIN CONSULTING AS

Who owns YOTDYRIN CONSULTING AS?

TORSTEIN THUN is the largest registered owner, with 100.0%.

What is the revenue of YOTDYRIN CONSULTING AS?

YOTDYRIN CONSULTING AS had revenue of NOK 0 in 2025.

Who is the general manager of YOTDYRIN CONSULTING AS?

Torstein Thun is registered as general manager of YOTDYRIN CONSULTING AS.

Where is YOTDYRIN CONSULTING AS based?

YOTDYRIN CONSULTING AS has its business address in Drammen.

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.