BIZTRAC BETA
Activities of advertising agencies

BAREKSTEN HOLDING AS

Org. no. 926660225 Limited company (AS) Ås Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 27,000
Equity NOK −141,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−141k kr).

BAREKSTEN HOLDING AS is registered as a limited company in Ås, Akershus with organisation number 926660225. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Hovedkontortjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 27,000
Equity
NOK −141,000
Est. value
NOK 109,000

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-28.1%
Weak
Equity as a share of total capital

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

Who owns BAREKSTEN HOLDING AS?

No shareholders are registered for BAREKSTEN HOLDING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does BAREKSTEN HOLDING AS own?

BAREKSTEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BAREKSTEN HOLDING AS

What is the revenue of BAREKSTEN HOLDING AS?

BAREKSTEN HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of BAREKSTEN HOLDING AS?

Stig Bareksten is registered as general manager of BAREKSTEN HOLDING AS.

Where is BAREKSTEN HOLDING AS based?

BAREKSTEN HOLDING AS has its business address in Vinterbro.

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.