BIZTRAC BETA
Freight transport by road

JK BETONGPUMPING AS

Org. no. 989823264 Limited company (AS) Time Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK −213,000
Equity NOK 1.7m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−213k kr).

JK BETONGPUMPING AS is registered as a limited company in Time, Rogaland with organisation number 989823264. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Betongpumping og hva herved står i forbindelse, samt innhøsting av gress og plantemangfold.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −213,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK −213,000
Equity
NOK 1.7m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns JK BETONGPUMPING AS?

JOHN KARSTEN THRANE ØGLÆND
JK BETONGPUMPING AS
NOK 2.1m rev. · NOK −213,000 profit

JK BETONGPUMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JK BETONGPUMPING AS

Who owns JK BETONGPUMPING AS?

JOHN KARSTEN THRANE ØGLÆND is the largest registered owner, with 100.0%.

What is the revenue of JK BETONGPUMPING AS?

JK BETONGPUMPING AS had revenue of NOK 2.1m in 2025.

Who is the general manager of JK BETONGPUMPING AS?

John Karsten Thrane Øglænd is registered as general manager of JK BETONGPUMPING AS.

Where is JK BETONGPUMPING AS based?

JK BETONGPUMPING AS has its business address in Bryne.

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.