BIZTRAC BETA
COMPANY REGISTER PROFILE
930825506 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer consultancy and computer facilities management activities

ANALYSEHUSET AS

Org. no. 930825506 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 403,000
Operating profit NOK 153,000
Equity NOK 151,000
Incorporated 2022
Share capital NOK 30,000

ANALYSEHUSET AS is registered as a limited company in Oslo, Oslo with organisation number 930825506. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Strategisk rådgivning og konsulenttjenester innen informasjonsteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 403,000 in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 403,000
Operating profit
NOK 153,000
Equity
NOK 151,000
Est. value
NOK 683,000

Financial health · 2025

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

Who owns ANALYSEHUSET AS?

ANALYSEHUSET HOLDING AS
ANALYSEHUSET AS
NOK 403,000 rev. · NOK 153,000 profit

ANALYSEHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANALYSEHUSET AS

Who owns ANALYSEHUSET AS?

ANALYSEHUSET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ANALYSEHUSET AS?

ANALYSEHUSET AS had revenue of NOK 403,000 in 2025.

Who is the general manager of ANALYSEHUSET AS?

Hamza Ali Ahmad is registered as general manager of ANALYSEHUSET AS.

Where is ANALYSEHUSET AS based?

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