biztrac. BETA
COMPANY REGISTER PROFILE
919420278 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Publishing of journals and periodicals

BILBRANSJENYTT AS

Org. no. 919420278 Limited company (AS) Oslo Incorporated 2017 Active
Operating profit NOK −16,000
Equity NOK −60,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

BILBRANSJENYTT AS is registered as a limited company in Oslo, Oslo with organisation number 919420278. The business is classified under publishing of journals and periodicals (NACE 58.130). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie og forvalte rettigheter (varemerker, internettadresser, domener med videre) til papir- og nettbaserte publikasjoner med referanse til bilbransjen, enten direkte eller ved eie av aksjer samt selv å arrangere - og/eller å levere tjenester til andre arrangører av - konferanser, messer, kurs og events i tilknytning til bilbransjen og tilstøtende bransjer samt hva som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −16,000
▼ −21 %
Equity
NOK −60,000
▼ −33 %

Financial health · 2025

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

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

Who owns BILBRANSJENYTT AS?

BILBRANSJENYTT AS
· NOK −16,000 profit

BILBRANSJENYTT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILBRANSJENYTT AS

Who owns BILBRANSJENYTT AS?

FAGBLADFORLAGET AS is the largest registered owner, with 100.0%.

Where is BILBRANSJENYTT AS based?

BILBRANSJENYTT 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.