BIZTRAC BETA
Computer programming activities

WEBBERNE AS

Org. no. 928966054 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 580,000
Operating profit NOK −12,000
Equity NOK 4,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

WEBBERNE AS is registered as a limited company in Moss, Østfold with organisation number 928966054. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Design og produksjon av nettsider, digital markedsføring, markedskommunikasjon, mediaproduksjon, rådgivning, coaching samt undervisning.”. The most recent filed accounts, for the 2024 financial year, show NOK 580,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 580,000
Operating profit
NOK −12,000
Equity
NOK 4,000
Est. value
NOK 981,000

Financial health · 2024

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

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

Who owns WEBBERNE AS?

SELAHATTIN LEVENT ULTANUR
WEBBERNE AS
NOK 580,000 rev. · NOK −12,000 profit

WEBBERNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WEBBERNE AS

Who owns WEBBERNE AS?

SELAHATTIN LEVENT ULTANUR is the largest registered owner, with 100.0%.

What is the revenue of WEBBERNE AS?

WEBBERNE AS had revenue of NOK 580,000 in 2024.

Who is the general manager of WEBBERNE AS?

Selahattin Levent Ultanur is registered as general manager of WEBBERNE AS.

Where is WEBBERNE AS based?

WEBBERNE AS has its business address in Moss.

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.