BIZTRAC BETA
Public relations and communication activities

GJEMMEKONTOR AS

Org. no. 998656745 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −18,000
Equity NOK 58,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

GJEMMEKONTOR AS is registered as a limited company in Oslo, Oslo with organisation number 998656745. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor PR og administrasjon, forfattervirksomhet og investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −18,000
Equity
NOK 58,000
Est. value
NOK 35,000

Financial health · 2024

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

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

Who owns GJEMMEKONTOR AS?

ASLE SKREDDERBERGET
GJEMMEKONTOR AS
NOK 7,000 rev. · NOK −18,000 profit

GJEMMEKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJEMMEKONTOR AS

Who owns GJEMMEKONTOR AS?

ASLE SKREDDERBERGET is the largest registered owner, with 100.0%.

What is the revenue of GJEMMEKONTOR AS?

GJEMMEKONTOR AS had revenue of NOK 7,000 in 2024.

Who is the general manager of GJEMMEKONTOR AS?

Asle Skredderberget is registered as general manager of GJEMMEKONTOR AS.

Where is GJEMMEKONTOR AS based?

GJEMMEKONTOR 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 15.06.2026.

Report a problem

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