BIZTRAC BETA
Retail sale of other new goods

VEDØRA BJØRK OG BRENSEL AS

Org. no. 991278184 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK 2,000
Equity NOK 95,000
Incorporated 2007
Employees 10
Share capital NOK 120,000

VEDØRA BJØRK OG BRENSEL AS is registered as a limited company in Oslo, Oslo with organisation number 991278184. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2007 and has 10 registered employees. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Salg av fyringsved og relevante tilhørlige forbruksartikler gjennom nettbutikk med tilhørende levering hjem og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK 2,000
Equity
NOK 95,000
Est. value
NOK 50,000

Financial health · 2024

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

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

Who owns VEDØRA BJØRK OG BRENSEL AS?

QVARNSJÖ SKOGSTJÄNSTER AB
VEDØRA BJØRK OG BRENSEL AS
NOK 3,000 rev. · NOK 2,000 profit

VEDØRA BJØRK OG BRENSEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEDØRA BJØRK OG BRENSEL AS

Who owns VEDØRA BJØRK OG BRENSEL AS?

QVARNSJÖ SKOGSTJÄNSTER AB is the largest registered owner, with 100.0%.

What is the revenue of VEDØRA BJØRK OG BRENSEL AS?

VEDØRA BJØRK OG BRENSEL AS had revenue of NOK 3,000 in 2024.

Where is VEDØRA BJØRK OG BRENSEL AS based?

VEDØRA BJØRK OG BRENSEL AS has its business address in Oslo.

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.