biztrac. BETA
COMPANY REGISTER PROFILE
933571033 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Private tuition

TORGRIM DALING AS

Org. no. 933571033 Limited company (AS) Melhus Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 154,000
Operating profit NOK 98,000
Equity NOK 346,000
Incorporated 2024
Share capital NOK 30,000

TORGRIM DALING AS is registered as a limited company in Melhus, Trøndelag with organisation number 933571033. The business is classified under private tuition (NACE 85.594). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Undervisning i videregående skole, arbeid innen landbruk samt bygningsvedlikehold. Selskapet kan engasjere seg i annen virksomhet ved aksjekjøp eller lignende.”. The most recent filed accounts, for the 2025 financial year, show NOK 154,000 in revenue and NOK 98,000 in operating profit.

Key figures · 2025

Revenue
NOK 154,000
▼ −60 %
Operating profit
NOK 98,000
▼ −69 %
Equity
NOK 346,000
▲ +28 %
Est. value
NOK 775,000

Financial health · 2025

Liquidity
11.56
Very good
Current assets ÷ current liabilities
Profitability
27.0%
Very good
Return on total assets
Solidity
91.3%
Very good
Equity as a share of total capital

Who owns TORGRIM DALING AS?

TORGRIM DALING AS
NOK 154,000 rev. · NOK 98,000 profit

TORGRIM DALING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORGRIM DALING AS

Who owns TORGRIM DALING AS?

Torgrim Daling is the largest registered owner, with 100.0%.

What is the revenue of TORGRIM DALING AS?

TORGRIM DALING AS had revenue of NOK 154,000 in 2025.

Who is the general manager of TORGRIM DALING AS?

Torgrim Daling is registered as general manager of TORGRIM DALING AS.

Where is TORGRIM DALING AS based?

TORGRIM DALING AS has its business address in Melhus.

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.