biztrac. BETA
COMPANY REGISTER PROFILE
993857149 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Miscellaneous vehicular training excluding authorised driving schools

DK FØRERUTVIKLING DANIEL KUBBERØD

Org. no. 993857149 Sole proprietorship (ENK) Våler Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.3m
Equity NOK −5,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).

DK FØRERUTVIKLING DANIEL KUBBERØD is registered as a sole proprietorship in Våler, Østfold with organisation number 993857149. The business is classified under miscellaneous vehicular training excluding authorised driving schools (NACE 85.532). The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.3m in operating profit.

Former names: KUBBERØD RACING, Daniel Kubberød

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.3m
Equity
NOK −5,000
Est. value
NOK 7.1m

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1.0%
Weak
Equity as a share of total capital

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

Who owns DK FØRERUTVIKLING DANIEL KUBBERØD?

No shareholders are registered for DK FØRERUTVIKLING DANIEL KUBBERØD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about DK FØRERUTVIKLING DANIEL KUBBERØD

What is the revenue of DK FØRERUTVIKLING DANIEL KUBBERØD?

DK FØRERUTVIKLING DANIEL KUBBERØD had revenue of NOK 2.2m in 2025.

Who is the general manager of DK FØRERUTVIKLING DANIEL KUBBERØD?

Daniel Kubberød is registered as general manager of DK FØRERUTVIKLING DANIEL KUBBERØD.

Where is DK FØRERUTVIKLING DANIEL KUBBERØD based?

DK FØRERUTVIKLING DANIEL KUBBERØD has its business address in Sperrebotn.

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.