BIZTRAC BETA
Retail sale of newspapers, and other periodical publications and stationery

LISBET BJØRNSTAD AS

Org. no. 920664199 Limited company (AS) Nes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 584,000
Operating profit NOK −99,000
Equity NOK 104,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

LISBET BJØRNSTAD AS is registered as a limited company in Nes, Akershus with organisation number 920664199. The business is classified under retail sale of newspapers, and other periodical publications and stationery (NACE 47.620). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av varer i nettbutikk. Transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 584,000 in revenue and NOK −99,000 in operating profit.

Key figures · 2025

Revenue
NOK 584,000
Operating profit
NOK −99,000
Equity
NOK 104,000
Est. value
NOK 239,000

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.6%
Very good
Equity as a share of total capital

Who owns LISBET BJØRNSTAD AS?

LISBET BJØRNSTAD
LISBET BJØRNSTAD AS
NOK 584,000 rev. · NOK −99,000 profit

LISBET BJØRNSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LISBET BJØRNSTAD AS

Who owns LISBET BJØRNSTAD AS?

LISBET BJØRNSTAD is the largest registered owner, with 100.0%.

What is the revenue of LISBET BJØRNSTAD AS?

LISBET BJØRNSTAD AS had revenue of NOK 584,000 in 2025.

Who is the general manager of LISBET BJØRNSTAD AS?

Lisbet Bjørnstad is registered as general manager of LISBET BJØRNSTAD AS.

Where is LISBET BJØRNSTAD AS based?

LISBET BJØRNSTAD AS has its business address in Årnes.

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.