BIZTRAC BETA
Other support activities for transportation

GASTON SCHUL CUSTOMS AS

Org. no. 912509184 Limited company (AS) Ullensaker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 8.1m
Operating profit NOK 251,000
Equity NOK 1.7m
Incorporated 2013
Share capital NOK 30,000

GASTON SCHUL CUSTOMS AS is registered as a limited company in Ullensaker, Akershus with organisation number 912509184. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg og formidling av spedisjon-fortollingstjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.1m in revenue and NOK 251,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.1m
Operating profit
NOK 251,000
Equity
NOK 1.7m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns GASTON SCHUL CUSTOMS AS?

GASTON SCHUL INTERNATIONAL BV
GASTON SCHUL CUSTOMS AS
NOK 8.1m rev. · NOK 251,000 profit

GASTON SCHUL CUSTOMS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GASTON SCHUL CUSTOMS AS

Who owns GASTON SCHUL CUSTOMS AS?

GASTON SCHUL INTERNATIONAL BV is the largest registered owner, with 100.0%.

What is the revenue of GASTON SCHUL CUSTOMS AS?

GASTON SCHUL CUSTOMS AS had revenue of NOK 8.1m in 2025.

Where is GASTON SCHUL CUSTOMS AS based?

GASTON SCHUL CUSTOMS AS has its business address in Kløfta.

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.