BIZTRAC BETA
Other captive investment companies

TRENING FOR DEG NORGE AS

Org. no. 994000578 Limited company (AS) Holmestrand Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 44,000
Operating profit NOK 41,000
Equity NOK 338,000
Incorporated 2009
Share capital NOK 100,000

TRENING FOR DEG NORGE AS is registered as a limited company in Holmestrand, Vestfold with organisation number 994000578. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tilrettelegging og drift av treningssenter, samt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 44,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 44,000
Operating profit
NOK 41,000
Equity
NOK 338,000
Est. value
NOK 311,000

Financial health · 2025

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

Who owns TRENING FOR DEG NORGE AS?

OLE JOHNNY HAUGEN
TRENING FOR DEG NORGE AS
NOK 44,000 rev. · NOK 41,000 profit

TRENING FOR DEG NORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRENING FOR DEG NORGE AS own?

TRENING FOR DEG NORGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRENING FOR DEG NORGE AS

Who owns TRENING FOR DEG NORGE AS?

OLE JOHNNY HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of TRENING FOR DEG NORGE AS?

TRENING FOR DEG NORGE AS had revenue of NOK 44,000 in 2025.

Where is TRENING FOR DEG NORGE AS based?

TRENING FOR DEG NORGE AS has its business address in Sande I Vestfold.

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.