BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

SCRAPPEGARASJEN AS

Org. no. 913520831 Limited company (AS) Lindesnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 339,000
Equity NOK 391,000
Incorporated 2014
Share capital NOK 30,000

SCRAPPEGARASJEN AS is registered as a limited company in Lindesnes, Agder with organisation number 913520831. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel med utstyr til hobby og produkter som naturlig hører sammen med dette, samt annen virksonhet som hermed står i forbindelse, inkludert deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 339,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 339,000
Equity
NOK 391,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns SCRAPPEGARASJEN AS?

JUNE CHRISTENSEN ALFSVÅG
SCRAPPEGARASJEN AS
NOK 2.1m rev. · NOK 339,000 profit

SCRAPPEGARASJEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SCRAPPEGARASJEN AS

Who owns SCRAPPEGARASJEN AS?

JUNE CHRISTENSEN ALFSVÅG is the largest registered owner, with 50.0%.

What is the revenue of SCRAPPEGARASJEN AS?

SCRAPPEGARASJEN AS had revenue of NOK 2.1m in 2024.

Who is the general manager of SCRAPPEGARASJEN AS?

June Christensen Alfsvåg is registered as general manager of SCRAPPEGARASJEN AS.

Where is SCRAPPEGARASJEN AS based?

SCRAPPEGARASJEN AS has its business address in Mandal.

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.