BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

CRAWLERCRANE AS

Org. no. 826324392 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 51,000
Equity NOK 3.0m
Incorporated 2020
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CRAWLERCRANE AS is registered as a limited company in Oslo, Oslo with organisation number 826324392. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2020. Registered share capital is NOK 3.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av kraner med tilhørende utstyr, samt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 51,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 51,000
Equity
NOK 3.0m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns CRAWLERCRANE AS?

BLUE GROUP AS
CRAWLERCRANE AS
NOK 5.3m rev. · NOK 51,000 profit

CRAWLERCRANE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

CRAWLERCRANE AS er morselskap for 18 datterselskaper:

Frequently asked questions about CRAWLERCRANE AS

Who owns CRAWLERCRANE AS?

BLUE GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of CRAWLERCRANE AS?

CRAWLERCRANE AS had revenue of NOK 5.3m in 2024.

Where is CRAWLERCRANE AS based?

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