BIZTRAC BETA
Activities of advertising agencies

KULDING AS

Org. no. 966619724 Limited company (AS) Drammen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −75,000
Equity NOK 942,000
Incorporated 1993
Share capital NOK 104,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−75k kr).

KULDING AS is registered as a limited company in Drammen, Buskerud with organisation number 966619724. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 1993. Registered share capital is NOK 104,000, divided into 104 shares. The company's stated purpose is: “Kjøp, salg og formidling av reklameprodukter samt andre relaterte produkter og tjnester og agentvirksomhet. Det skal være anledning til å eie aksjer og andeler i andre selskaper, samt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −75,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −75,000
Equity
NOK 942,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns KULDING AS?

THOMAS KULBERG
KULDING AS
NOK 1.2m rev. · NOK −75,000 profit

KULDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KULDING AS own?

KULDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KULDING AS

Who owns KULDING AS?

THOMAS KULBERG is the largest registered owner, with 100.0%.

What is the revenue of KULDING AS?

KULDING AS had revenue of NOK 1.2m in 2024.

Where is KULDING AS based?

KULDING AS has its business address in Drammen.

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.