BIZTRAC BETA
Leasing of intellectual property and similar products, except copyrighted works

GAMMEL NOK FRANCHISE AS

Org. no. 823541082 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK −1.8m
Incorporated 2019
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GAMMEL NOK FRANCHISE AS is registered as a limited company in Asker, Akershus with organisation number 823541082. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Leasing av immateriell eiendom, drift av franchisevirksomhet, deltakelse i andre selskaper, samt enhver virksomhet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −46,000
Equity
NOK −1.8m

Financial health · 2025

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

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

Who owns GAMMEL NOK FRANCHISE AS?

GAMMEL NOK HOLDING AS
GAMMEL NOK FRANCHISE AS
· NOK −46,000 profit

GAMMEL NOK FRANCHISE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMMEL NOK FRANCHISE AS

Who owns GAMMEL NOK FRANCHISE AS?

GAMMEL NOK HOLDING AS is the largest registered owner, with 100.0%.

Where is GAMMEL NOK FRANCHISE AS based?

GAMMEL NOK FRANCHISE AS has its business address in Asker.

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.