BIZTRAC BETA
COMPANY REGISTER PROFILE
980268004 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ELSE S GJESTI

Org. no. 980268004 Sole proprietorship (ENK) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 262,000
Operating profit NOK −111,000
Equity NOK 73,000

Signals

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

ELSE S GJESTI is registered as a sole proprietorship in Oslo, Oslo with organisation number 980268004. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 262,000 in revenue and NOK −111,000 in operating profit.

Former names: ADVOKAT ELSE S GJESTI

Key figures · 2025

Revenue
NOK 262,000
Operating profit
NOK −111,000
Equity
NOK 73,000
Est. value
NOK 311,000

Financial health · 2025

Liquidity
2.69
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.8%
Weak
Equity as a share of total capital

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

Who owns ELSE S GJESTI?

No shareholders are registered for ELSE S GJESTI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ELSE S GJESTI

What is the revenue of ELSE S GJESTI?

ELSE S GJESTI had revenue of NOK 262,000 in 2025.

Where is ELSE S GJESTI based?

ELSE S GJESTI has its business address in Oslo.

Property

Business address Karl Johans gate 41A, 0162 Oslo
Cadastral unit 301-209/139/0/0
Building Butikkbygning · 5 units

20 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.