BIZTRAC BETA
Computer consultancy and computer facilities management activities

NORWEKA AS

Org. no. 933170705 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1.3m
Equity NOK 231,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

NORWEKA AS is registered as a limited company in Lillestrøm, Akershus with organisation number 933170705. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1.3m
Equity
NOK 231,000
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns NORWEKA AS?

NORWEKA GROUP AS
NORWEKA AS
NOK 3.0m rev. · NOK 1.3m profit

NORWEKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORWEKA AS

Who owns NORWEKA AS?

NORWEKA GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of NORWEKA AS?

NORWEKA AS had revenue of NOK 3.0m in 2024.

Who is the general manager of NORWEKA AS?

Joseph Fredy Pambi is registered as general manager of NORWEKA AS.

Where is NORWEKA AS based?

NORWEKA AS has its business address in Lillestrøm.

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.