biztrac. BETA
COMPANY REGISTER PROFILE
924499273 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

JW CRANE CONSULT AS

Org. no. 924499273 Limited company (AS) Flekkefjord Incorporated 2020 Active
Revenue 2025 NOK 316,000
Operating profit NOK 297,000
Equity NOK 715,000
Incorporated 2020
Share capital NOK 30,000

JW CRANE CONSULT AS is registered as a limited company in Flekkefjord, Agder with organisation number 924499273. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester primært rettet mot olje/gass industri med hovedvekt på fagområdet kran, løft og materialhåndtering.”. The most recent filed accounts, for the 2025 financial year, show NOK 316,000 in revenue and NOK 297,000 in operating profit.

Key figures · 2025

Revenue
NOK 316,000
▲ +22 %
Operating profit
NOK 297,000
▲ +21 %
Equity
NOK 715,000
▲ +49 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
11.72
Very good
Current assets ÷ current liabilities
Profitability
45.7%
Very good
Return on total assets
Solidity
91.5%
Very good
Equity as a share of total capital

Who owns JW CRANE CONSULT AS?

JW CRANE CONSULT AS
NOK 316,000 rev. · NOK 297,000 profit

JW CRANE CONSULT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JW CRANE CONSULT AS

Who owns JW CRANE CONSULT AS?

Johnny Westnes is the largest registered owner, with 50.0%.

What is the revenue of JW CRANE CONSULT AS?

JW CRANE CONSULT AS had revenue of NOK 316,000 in 2025.

Who is the general manager of JW CRANE CONSULT AS?

Johnny Westnes is registered as general manager of JW CRANE CONSULT AS.

Where is JW CRANE CONSULT AS based?

JW CRANE CONSULT AS has its business address in Flekkefjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.