BIZTRAC BETA
COMPANY REGISTER PROFILE
928957063 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

OMNY AS

Org. no. 928957063 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 42.9m
Operating profit NOK −64.6m
Equity NOK 30.4m
Incorporated 2022
Employees 54
Share capital NOK 271,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−64,6 mill kr).

OMNY AS is registered as a limited company in Bærum, Akershus with organisation number 928957063. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022 and has 54 registered employees. Registered share capital is NOK 271,000, divided into 271280000 shares. The company's stated purpose is: “Utvikling og investering i andre selskaper og alt som står i forbindelse med forannevnte virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 42.9m in revenue and NOK −64.6m in operating profit.

Former names: NFH 220309 AS

Key figures · 2025

Revenue
NOK 42.9m
▲ +247 %
Operating profit
NOK −64.6m
▲ +13 %
Equity
NOK 30.4m
▲ +230 %
Est. value
NOK 80.6m

Financial health · 2025

Liquidity
2.00
Good
Current assets ÷ current liabilities
Profitability
-112.9%
Not satisfactory
Return on total assets
Solidity
45.3%
Very good
Equity as a share of total capital

Who owns OMNY AS?

OMNY AS
NOK 42.9m rev. · NOK −64.6m profit

OMNY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMNY AS

Who owns OMNY AS?

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

What is the revenue of OMNY AS?

OMNY AS had revenue of NOK 42.9m in 2025.

Who is the general manager of OMNY AS?

Thomas Fetten is registered as general manager of OMNY AS.

Where is OMNY AS based?

OMNY AS has its business address in Lysaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.