biztrac. BETA
COMPANY REGISTER PROFILE
926607537 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other postal and courier activities

BE STILL AS

Org. no. 926607537 Limited company (AS) Ringerike Incorporated 2021 Active
Revenue 2025 NOK 1.2m
Operating profit NOK −127,000
Equity NOK −124,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−124k kr).

BE STILL AS is registered as a limited company in Ringerike, Buskerud with organisation number 926607537. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Hjemlevering av restaurantmat.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −127,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +16 %
Operating profit
NOK −127,000
▼ −841 %
Equity
NOK −124,000
▼ −985 %

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
-26.9%
Not satisfactory
Return on total assets
Solidity
-34.6%
Weak
Equity as a share of total capital

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

Who owns BE STILL AS?

BE STILL AS
NOK 1.2m rev. · NOK −127,000 profit

BE STILL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BE STILL AS

Who owns BE STILL AS?

Hafez Ahmed Hafez Almyet Yathedy is the largest registered owner, with 100.0%.

What is the revenue of BE STILL AS?

BE STILL AS had revenue of NOK 1.2m in 2025.

Who is the general manager of BE STILL AS?

Hafez Ahmed Hafez Almyet Yathedy is registered as general manager of BE STILL AS.

Where is BE STILL AS based?

BE STILL AS has its business address in Hønefoss.

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.