BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

VENSKA AS

Org. no. 918080341 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 718,000
Operating profit NOK −97,000
Equity NOK 499,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

VENSKA AS is registered as a limited company in Drammen, Buskerud with organisation number 918080341. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av vinduer samt andre byggevarer, entreprenørvirksomhet- boliger og industribygg, transport av varer, lagring og utkjøring av varer, montering av vinduer.”. The most recent filed accounts, for the 2024 financial year, show NOK 718,000 in revenue and NOK −97,000 in operating profit.

Key figures · 2024

Revenue
NOK 718,000
Operating profit
NOK −97,000
Equity
NOK 499,000
Est. value
NOK 471,000

Financial health · 2024

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

Who owns VENSKA AS?

MACIEJ KRZYSZTOF WENTA
VENSKA AS
NOK 718,000 rev. · NOK −97,000 profit

VENSKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VENSKA AS

Who owns VENSKA AS?

MACIEJ KRZYSZTOF WENTA is the largest registered owner, with 100.0%.

What is the revenue of VENSKA AS?

VENSKA AS had revenue of NOK 718,000 in 2024.

Who is the general manager of VENSKA AS?

Maciej Krzysztof Wenta is registered as general manager of VENSKA AS.

Where is VENSKA AS based?

VENSKA 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.