BIZTRAC BETA
Tanning, dressing, dyeing of leather and fur

GLOTRADE AS

Org. no. 914350565 Limited company (AS) Klepp Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 390,000
Operating profit NOK 174,000
Equity NOK 2.4m
Incorporated 2014
Share capital NOK 50,000

GLOTRADE AS is registered as a limited company in Klepp, Rogaland with organisation number 914350565. The business is classified under tanning, dressing, dyeing of leather and fur (NACE 15.110). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Pelsing og bearbeiding av skinn, kjøp og videresalg av animalske biprodukt, samt annen virksomhet som naturlig kan knyttes til dette. Kjøp og salg av aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 390,000 in revenue and NOK 174,000 in operating profit.

Key figures · 2024

Revenue
NOK 390,000
Operating profit
NOK 174,000
Equity
NOK 2.4m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns GLOTRADE AS?

PER ARILD VÅDELAND
GLOTRADE AS
NOK 390,000 rev. · NOK 174,000 profit

GLOTRADE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLOTRADE AS own?

GLOTRADE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GLOTRADE AS

Who owns GLOTRADE AS?

PER ARILD VÅDELAND is the largest registered owner, with 100.0%.

What is the revenue of GLOTRADE AS?

GLOTRADE AS had revenue of NOK 390,000 in 2024.

Who is the general manager of GLOTRADE AS?

Per Arild Vådeland is registered as general manager of GLOTRADE AS.

Where is GLOTRADE AS based?

GLOTRADE AS has its business address in Klepp Stasjon.

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.