BIZTRAC BETA
COMPANY REGISTER PROFILE
811744522 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

JANO AS

Org. no. 811744522 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −34,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 30,000

Signals

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

JANO AS is registered as a limited company in Bergen, Vestland with organisation number 811744522. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer, eiendom og andeler i andre selskaper, samt virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 1.1m
Est. value
NOK 610,000

Financial health · 2025

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

Who owns JANO AS?

JANNE NORE
JANO AS
NOK 0 rev. · NOK −34,000 profit

JANO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JANO AS own?

JANO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JANO AS

Who owns JANO AS?

JANNE NORE is the largest registered owner, with 100.0%.

What is the revenue of JANO AS?

JANO AS had revenue of NOK 0 in 2025.

Who is the general manager of JANO AS?

Janne Nore is registered as general manager of JANO AS.

Where is JANO AS based?

JANO AS has its business address in Hjellestad.

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.