BIZTRAC BETA
COMPANY REGISTER PROFILE
935796008 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

GREASY HOUSE AS

Org. no. 935796008 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 179,000
Operating profit NOK 51,000
Equity NOK 70,000
Incorporated 2025
Employees 8
Share capital NOK 30,000

GREASY HOUSE AS is registered as a limited company in Oslo, Oslo with organisation number 935796008. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av restauranter og kafeer, samt det som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 179,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 179,000
Operating profit
NOK 51,000
Equity
NOK 70,000
Est. value
NOK 182,000

Financial health · 2025

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.9%
Weak
Equity as a share of total capital

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

Who owns GREASY HOUSE AS?

NEZAMUDDIN SHAHABZAI
GREASY HOUSE AS
NOK 179,000 rev. · NOK 51,000 profit

GREASY HOUSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GREASY HOUSE AS

Who owns GREASY HOUSE AS?

NEZAMUDDIN SHAHABZAI is the largest registered owner, with 100.0%.

What is the revenue of GREASY HOUSE AS?

GREASY HOUSE AS had revenue of NOK 179,000 in 2025.

Who is the general manager of GREASY HOUSE AS?

Nezamuddin Shahabzai is registered as general manager of GREASY HOUSE AS.

Where is GREASY HOUSE AS based?

GREASY HOUSE 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.