BIZTRAC BETA
COMPANY REGISTER PROFILE
968434640 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

DETALJCONSULT Ove Syslak

Org. no. 968434640 Sole proprietorship (ENK) Ullensaker Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 0

DETALJCONSULT Ove Syslak is registered as a sole proprietorship in Ullensaker, Akershus with organisation number 968434640. The business is classified under business and other management consultancy activities (NACE 70.200). The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns DETALJCONSULT Ove Syslak?

No shareholders are registered for DETALJCONSULT Ove Syslak in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about DETALJCONSULT Ove Syslak

What is the revenue of DETALJCONSULT Ove Syslak?

DETALJCONSULT Ove Syslak had revenue of NOK 0 in 2024.

Where is DETALJCONSULT Ove Syslak based?

DETALJCONSULT Ove Syslak has its business address in Kløfta.

Property

Business address Guri Øverbys veg 24, 2040 Kløfta
Cadastral unit 3209-29/1102/0/0
Building Store sammenbygde boligbygg på 5 el mer · 33 units

5 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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