biztrac. BETA
COMPANY REGISTER PROFILE
934997565 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

HUDE AS

Org. no. 934997565 Limited company (AS) Lørenskog Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 1,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HUDE AS is registered as a limited company in Lørenskog, Akershus with organisation number 934997565. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 1,000
Est. value
NOK 2,000

Financial health · 2025

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

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

Who owns HUDE AS?

HUDE AS
NOK 0 rev. · NOK −22,000 profit

HUDE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUDE AS

Who owns HUDE AS?

Frode Nogva Flem is the largest registered owner, with 50.0%.

What is the revenue of HUDE AS?

HUDE AS had revenue of NOK 0 in 2025.

Who is the general manager of HUDE AS?

Frode Nogva Flem is registered as general manager of HUDE AS.

Where is HUDE AS based?

HUDE AS has its business address in Lørenskog.

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.