biztrac. BETA
COMPANY REGISTER PROFILE
929166868 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Intermediation service activities for courses and tutors

IDRETTSKONCULT AS

Org. no. 929166868 Limited company (AS) Holmestrand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 231,000
Operating profit NOK 6,000
Equity NOK 8,000
Incorporated 2022
Share capital NOK 30,000

IDRETTSKONCULT AS is registered as a limited company in Holmestrand, Vestfold with organisation number 929166868. The business is classified under intermediation service activities for courses and tutors (NACE 85.610). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulent innenfor idretts og arrangement, spillemiddelsøknader, beredskaps- sikkerhetsplaner for arrangement med mer.”. The most recent filed accounts, for the 2025 financial year, show NOK 231,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 231,000
▼ −9 %
Operating profit
NOK 6,000
▼ −79 %
Equity
NOK 8,000
▼ −44 %
Est. value
NOK 79,000

Financial health · 2025

Liquidity
1.78
Good
Current assets ÷ current liabilities
Profitability
32.6%
Very good
Return on total assets
Solidity
45.1%
Weak
Equity as a share of total capital

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

Who owns IDRETTSKONCULT AS?

IDRETTSKONCULT AS
NOK 231,000 rev. · NOK 6,000 profit

IDRETTSKONCULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IDRETTSKONCULT AS

Who owns IDRETTSKONCULT AS?

Tommy Svendsrud is the largest registered owner, with 100.0%.

What is the revenue of IDRETTSKONCULT AS?

IDRETTSKONCULT AS had revenue of NOK 231,000 in 2025.

Where is IDRETTSKONCULT AS based?

IDRETTSKONCULT 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.