BIZTRAC BETA
Event catering activities

NICAST AS

Org. no. 931434276 Limited company (AS) Ås Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 602,000
Operating profit NOK 97,000
Equity NOK 484,000
Incorporated 2023
Share capital NOK 30,000

NICAST AS is registered as a limited company in Ås, Akershus with organisation number 931434276. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kursvirksomhet, events, konsulenttjenester, rådgivning, endringshåndtering, endringsledelse, rekruttering, utleie, drift av cafe, bar og restaurant, tjenesteyting og konsulentvirksomhet rettet mot hotell og restaurantbransjen og andre diverse bransjer, samt deltagelse i selskaper med samme eller tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 602,000 in revenue and NOK 97,000 in operating profit.

Key figures · 2025

Revenue
NOK 602,000
Operating profit
NOK 97,000
Equity
NOK 484,000
Est. value
NOK 680,000

Financial health · 2025

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

Who owns NICAST AS?

GUSTAV PATRIK ERIKSSON
NICAST AS
NOK 602,000 rev. · NOK 97,000 profit

NICAST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NICAST AS

Who owns NICAST AS?

GUSTAV PATRIK ERIKSSON is the largest registered owner, with 100.0%.

What is the revenue of NICAST AS?

NICAST AS had revenue of NOK 602,000 in 2025.

Who is the general manager of NICAST AS?

Gustav Patrik Eriksson is registered as general manager of NICAST AS.

Where is NICAST AS based?

NICAST AS has its business address in Vinterbro.

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.