BIZTRAC BETA
Other educational support services n.e.c.

RUNE SVEBERG AS

Org. no. 997934806 Limited company (AS) Larvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 37,000
Incorporated 2012
Share capital NOK 50,000

Signals

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

RUNE SVEBERG AS is registered as a limited company in Larvik, Vestfold with organisation number 997934806. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Rådgivningsvirksomhet og hva som dermed står i forbindelse, herunder også deltakelse i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 37,000
Est. value
NOK 54,000

Financial health · 2025

Liquidity
34.30
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.5%
Weak
Equity as a share of total capital

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

Who owns RUNE SVEBERG AS?

RUNE SVEBERG
RUNE SVEBERG AS
NOK 0 rev. · NOK −4,000 profit

RUNE SVEBERG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUNE SVEBERG AS

Who owns RUNE SVEBERG AS?

RUNE SVEBERG is the largest registered owner, with 70.0%.

What is the revenue of RUNE SVEBERG AS?

RUNE SVEBERG AS had revenue of NOK 0 in 2025.

Who is the general manager of RUNE SVEBERG AS?

Rune Sveberg is registered as general manager of RUNE SVEBERG AS.

Where is RUNE SVEBERG AS based?

RUNE SVEBERG AS has its business address in Larvik.

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.