BIZTRAC BETA
COMPANY REGISTER PROFILE
821026172 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

FOODSTOCK AS

Org. no. 821026172 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK −1,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

FOODSTOCK AS is registered as a limited company in Oslo, Oslo with organisation number 821026172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investeringer i aksjer, eiendom og annen relatert virksomhet.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK −1,000

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-119.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FOODSTOCK AS?

FOODSTOCK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOODSTOCK AS

Who owns FOODSTOCK AS?

BMG EIENDOM AS is the largest registered owner, with 50.0%.

Where is FOODSTOCK AS based?

FOODSTOCK AS has its business address in Oslo.

Property

Business address Kittel-Nielsens vei 67C, 1163 Oslo
Cadastral unit 301-183/241/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.