biztrac. BETA
COMPANY REGISTER PROFILE
936127266 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

HUMAQ AS

Org. no. 936127266 Limited company (AS) Nesodden Incorporated 2025 Active
Revenue 2025 NOK 5,000
Operating profit NOK −26,000
Equity NOK 4,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

HUMAQ AS is registered as a limited company in Nesodden, Akershus with organisation number 936127266. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning, utvikling av tjenester, salg og utleie varer til næringslivet og helsesektor.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −26,000
Equity
NOK 4,000
Est. value
NOK 7,000

Financial health · 2025

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

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

Who owns HUMAQ AS?

HUMAQ AS
NOK 5,000 rev. · NOK −26,000 profit

HUMAQ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUMAQ AS

Who owns HUMAQ AS?

Lars Erik Måseide is the largest registered owner, with 100.0%.

What is the revenue of HUMAQ AS?

HUMAQ AS had revenue of NOK 5,000 in 2025.

Who is the general manager of HUMAQ AS?

Lars Erik Måseide is registered as general manager of HUMAQ AS.

Where is HUMAQ AS based?

HUMAQ AS has its business address in Nesodden.

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.