BIZTRAC BETA
Wholesale of clothing and footwear

BULLDOG PROTECTIVE WORKWEAR AS

Org. no. 934758986 Limited company (AS) Tysvær Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 157,000
Equity NOK 4.1m
Incorporated 1983
Share capital NOK 140,000

BULLDOG PROTECTIVE WORKWEAR AS is registered as a limited company in Tysvær, Rogaland with organisation number 934758986. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 1983. Registered share capital is NOK 140,000, divided into 1395 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester innen personlig verneutstyr og arbeidstøy, samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 157,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 157,000
Equity
NOK 4.1m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns BULLDOG PROTECTIVE WORKWEAR AS?

KJETIL EIDESVIK AS
BULLDOG PROTECTIVE WORKWEAR AS
NOK 13.2m rev. · NOK 157,000 profit

BULLDOG PROTECTIVE WORKWEAR AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BULLDOG PROTECTIVE WORKWEAR AS

Who owns BULLDOG PROTECTIVE WORKWEAR AS?

KJETIL EIDESVIK AS is the largest registered owner, with 36.2%.

What is the revenue of BULLDOG PROTECTIVE WORKWEAR AS?

BULLDOG PROTECTIVE WORKWEAR AS had revenue of NOK 13.2m in 2024.

Where is BULLDOG PROTECTIVE WORKWEAR AS based?

BULLDOG PROTECTIVE WORKWEAR AS has its business address in Aksdal.

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.