BIZTRAC BETA
Sports and recreation education

BYIDA AS

Org. no. 992849487 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 952,000
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BYIDA AS is registered as a limited company in Larvik, Vestfold with organisation number 992849487. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Klesdesign, utvikling, kjøp og salg av brands, samt investering i selskaper tilknyttet dette. Selskapet skal også importere og videreselge varer direkte til butikker og butikkjeder samt å drive dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 952,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.9%
Very good
Equity as a share of total capital

Who owns BYIDA AS?

BRANDSÆTER HELGELAND AS
BYIDA AS
NOK 0 rev. · NOK −15,000 profit

BYIDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYIDA AS

Who owns BYIDA AS?

BRANDSÆTER HELGELAND AS is the largest registered owner, with 100.0%.

What is the revenue of BYIDA AS?

BYIDA AS had revenue of NOK 0 in 2024.

Where is BYIDA AS based?

BYIDA AS has its business address in Stavern.

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.