BIZTRAC BETA
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

RAMSLAND PUKK AS

Org. no. 981413148 Limited company (AS) Bjerkreim Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 6.4m
Operating profit NOK 68,000
Equity NOK 6.0m
Incorporated 1999
Share capital NOK 2.0m

Signals

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

RAMSLAND PUKK AS is registered as a limited company in Bjerkreim, Rogaland with organisation number 981413148. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 1999. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Drift av steinbrudd og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.4m in revenue and NOK 68,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.4m
Operating profit
NOK 68,000
Equity
NOK 6.0m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns RAMSLAND PUKK AS?

RAMSLAND AS
RAMSLAND PUKK AS
NOK 6.4m rev. · NOK 68,000 profit

RAMSLAND PUKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAMSLAND PUKK AS

Who owns RAMSLAND PUKK AS?

RAMSLAND AS is the largest registered owner, with 100.0%.

What is the revenue of RAMSLAND PUKK AS?

RAMSLAND PUKK AS had revenue of NOK 6.4m in 2024.

Who is the general manager of RAMSLAND PUKK AS?

Bjørnar Surdal is registered as general manager of RAMSLAND PUKK AS.

Where is RAMSLAND PUKK AS based?

RAMSLAND PUKK AS has its business address in Bjerkreim.

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.