biztrac. BETA
COMPANY REGISTER PROFILE
935342473 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

FAM GJELSETH AS

Org. no. 935342473 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 106,000
Operating profit NOK −192,000
Equity NOK 205.9m
Incorporated 2025
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−192k kr).

FAM GJELSETH AS is registered as a limited company in Oslo, Oslo with organisation number 935342473. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 120,000, divided into 40 shares. The company's stated purpose is: “Investeringer, eierskap i andre selskaper samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 106,000 in revenue and NOK −192,000 in operating profit.

Key figures · 2025

Revenue
NOK 106,000
Operating profit
NOK −192,000
Equity
NOK 205.9m
Est. value
NOK 272.8m

Financial health · 2025

Liquidity
33.17
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
79.5%
Very good
Equity as a share of total capital

Who owns FAM GJELSETH AS?

FAM GJELSETH AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FAM GJELSETH AS own?

FAM GJELSETH AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

FAM GJELSETH AS er morselskap for 7 datterselskaper:

Frequently asked questions about FAM GJELSETH AS

Who owns FAM GJELSETH AS?

MARKUS GJELSETH INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of FAM GJELSETH AS?

FAM GJELSETH AS had revenue of NOK 106,000 in 2025.

Where is FAM GJELSETH AS based?

FAM GJELSETH AS has its business address in Oslo.

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

Report a problem

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