BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

AGRIPA PROSJEKT AS

Org. no. 920770835 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 541,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 30,000

Signals

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

AGRIPA PROSJEKT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 920770835. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikle, selge og montere bygningsprodukter bstående av glass, aluminium og stål (metallarbeider) i alle type prosjekter for bedriftskunder, samt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 541,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK 541,000
Equity
NOK 1.9m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns AGRIPA PROSJEKT AS?

ZUM AS
AGRIPA PROSJEKT AS
NOK 5.8m rev. · NOK 541,000 profit

AGRIPA PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGRIPA PROSJEKT AS

Who owns AGRIPA PROSJEKT AS?

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

What is the revenue of AGRIPA PROSJEKT AS?

AGRIPA PROSJEKT AS had revenue of NOK 5.8m in 2025.

Where is AGRIPA PROSJEKT AS based?

AGRIPA PROSJEKT AS has its business address in Stokke.

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.