BIZTRAC BETA
COMPANY REGISTER PROFILE
924499273 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

JW CRANE CONSULT AS

Org. no. 924499273 Limited company (AS) Flekkefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 259,000
Operating profit NOK 247,000
Equity NOK 479,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 2024 financial year, show NOK 259,000 in revenue and NOK 247,000 in operating profit.

Key figures · 2024

Revenue
NOK 259,000
Operating profit
NOK 247,000
Equity
NOK 479,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns JW CRANE CONSULT AS?

JOHNNY WESTNES
JW CRANE CONSULT AS
NOK 259,000 rev. · NOK 247,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 259,000 in 2024.

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

Report a problem

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