BIZTRAC BETA
Computer consultancy and computer facilities management activities

DUCK & DUCK AS

Org. no. 934746686 Limited company (AS) Vestby Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 112,000
Equity NOK 102,000
Incorporated 2024
Share capital NOK 30,000

DUCK & DUCK AS is registered as a limited company in Vestby, Akershus with organisation number 934746686. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Konsulentvirksomhet innen webutvikling og ingeniørtjenester, videreformidling av tjenester for konsulenter og webutviklere, samt eie aksjer og andeler i andre selskap og alt som hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 112,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 112,000
Equity
NOK 102,000
Est. value
NOK 679,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.9%
Very good
Equity as a share of total capital

Who owns DUCK & DUCK AS?

RUSLAN KACHKOVSKYI
DUCK & DUCK AS
NOK 1.2m rev. · NOK 112,000 profit

DUCK & DUCK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUCK & DUCK AS

Who owns DUCK & DUCK AS?

RUSLAN KACHKOVSKYI is the largest registered owner, with 100.0%.

What is the revenue of DUCK & DUCK AS?

DUCK & DUCK AS had revenue of NOK 1.2m in 2025.

Who is the general manager of DUCK & DUCK AS?

Ruslan Kachkovskyi is registered as general manager of DUCK & DUCK AS.

Where is DUCK & DUCK AS based?

DUCK & DUCK AS has its business address in Vestby.

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.