BIZTRAC BETA
Freight transport by road

GARDERMOFRAKT AS

Org. no. 947300474 Limited company (AS) Oslo Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK −3.0m
Equity NOK 4.9m
Incorporated 1988
Share capital NOK 840,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,0 mill kr).

GARDERMOFRAKT AS is registered as a limited company in Oslo, Oslo with organisation number 947300474. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1988. Registered share capital is NOK 840,000, divided into 840000 shares. The company's stated purpose is: “Kjøpe, forvalte og omsette investeringer herunder andre selskaper bl.a aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK −3.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK −3.0m
Equity
NOK 4.9m
Est. value
NOK 15.4m

Financial health · 2024

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

Who owns GARDERMOFRAKT AS?

STÅLE BJØRDAL
GARDERMOFRAKT AS
NOK 5.2m rev. · NOK −3.0m profit

GARDERMOFRAKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GARDERMOFRAKT AS own?

GARDERMOFRAKT AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GARDERMOFRAKT AS

Who owns GARDERMOFRAKT AS?

STÅLE BJØRDAL is the largest registered owner, with 100.0%.

What is the revenue of GARDERMOFRAKT AS?

GARDERMOFRAKT AS had revenue of NOK 5.2m in 2024.

Who is the general manager of GARDERMOFRAKT AS?

Ståle Bjørdal is registered as general manager of GARDERMOFRAKT AS.

Where is GARDERMOFRAKT AS based?

GARDERMOFRAKT AS has its business address in Oslo.

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.