BIZTRAC BETA
Retail sale of other new goods

VEDEKSPRESSEN AS

Org. no. 933833488 Limited company (AS) Sarpsborg Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 88,000
Operating profit NOK −907
Equity NOK 29,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

VEDEKSPRESSEN AS is registered as a limited company in Sarpsborg, Østfold with organisation number 933833488. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og distribusjon av ved og andre relaterte produkter og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 88,000 in revenue and NOK −907 in operating profit.

Key figures · 2025

Revenue
NOK 88,000
Operating profit
NOK −907
Equity
NOK 29,000
Est. value
NOK 42,000

Financial health · 2025

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

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

Who owns VEDEKSPRESSEN AS?

JØRN ERIK TVETER-LARSEN
VEDEKSPRESSEN AS
NOK 88,000 rev. · NOK −907 profit

VEDEKSPRESSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEDEKSPRESSEN AS

Who owns VEDEKSPRESSEN AS?

JØRN ERIK TVETER-LARSEN is the largest registered owner, with 100.0%.

What is the revenue of VEDEKSPRESSEN AS?

VEDEKSPRESSEN AS had revenue of NOK 88,000 in 2025.

Who is the general manager of VEDEKSPRESSEN AS?

Jørn Erik Tveter-Larsen is registered as general manager of VEDEKSPRESSEN AS.

Where is VEDEKSPRESSEN AS based?

VEDEKSPRESSEN AS has its business address in Sarpsborg.

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.