biztrac. BETA
COMPANY REGISTER PROFILE
918585737 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Motion picture, video and television programme production activities

SØNDAGSKJÆRESTE AS

Org. no. 918585737 Limited company (AS) Oslo Incorporated 2017 Active
Operating profit NOK 0
Equity NOK −3.9m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,9 mill kr).

SØNDAGSKJÆRESTE AS is registered as a limited company in Oslo, Oslo with organisation number 918585737. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie og handle verdipapirer og annet som naturlig faller sammen med dette.”.

Former names: MOE THOMPSON AS

Key figures · 2025

Operating profit
NOK 0
▲ +100 %
Equity
NOK −3.9m
▼ −745 %

Financial health · 2025

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

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

Who owns SØNDAGSKJÆRESTE AS?

SØNDAGSKJÆRESTE AS
· NOK 0 profit

SØNDAGSKJÆRESTE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØNDAGSKJÆRESTE AS own?

SØNDAGSKJÆRESTE AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about SØNDAGSKJÆRESTE AS

Who owns SØNDAGSKJÆRESTE AS?

Anders Gravir Imenes is the largest registered owner, with 100.0%.

Who is the general manager of SØNDAGSKJÆRESTE AS?

Anders Gravir Imenes is registered as general manager of SØNDAGSKJÆRESTE AS.

Where is SØNDAGSKJÆRESTE AS based?

SØNDAGSKJÆRESTE 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.