BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

BREKKA SANDTAK AS

Org. no. 884237742 Limited company (AS) Grimstad Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 65,000
Operating profit NOK −38,000
Equity NOK 437,000
Incorporated 2002
Share capital NOK 414,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−38k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BREKKA SANDTAK AS is registered as a limited company in Grimstad, Agder with organisation number 884237742. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2002. Registered share capital is NOK 414,000, divided into 4136 shares. The company's stated purpose is: “Drift av sandtak, transport, samt gjenvinning av avfall og tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 65,000 in revenue and NOK −38,000 in operating profit.

Key figures · 2024

Revenue
NOK 65,000
Operating profit
NOK −38,000
Equity
NOK 437,000
Est. value
NOK 265,000

Financial health · 2024

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.6%
Good
Equity as a share of total capital

Who owns BREKKA SANDTAK AS?

APOTEKET EIENDOM AS
BREKKA SANDTAK AS
NOK 65,000 rev. · NOK −38,000 profit

BREKKA SANDTAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREKKA SANDTAK AS

Who owns BREKKA SANDTAK AS?

APOTEKET EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BREKKA SANDTAK AS?

BREKKA SANDTAK AS had revenue of NOK 65,000 in 2024.

Where is BREKKA SANDTAK AS based?

BREKKA SANDTAK AS has its business address in Grimstad.

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.