BIZTRAC BETA
Business and other management consultancy activities

BRÅTTSJY AS

Org. no. 936945201 Limited company (AS) Nesna Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK −5,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-15.

BRÅTTSJY AS is registered as a limited company in Nesna, Nordland with organisation number 936945201. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby rådgivings- og utviklingstjenester innen innovasjon, forretningsutvikling og prosjektfinansiering. Virksomheten skal bistå bedrifter og offentlige aktører med strategi, prosjektutvikling og gjennomføring, samt kunne eie eller delta i prosjekter og selskaper med beslektet virksomhet.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK −5,000

Financial health · 2025

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

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

Who owns BRÅTTSJY AS?

JOAKIM OLSEN EINMO
BRÅTTSJY AS
· NOK −7,000 profit

BRÅTTSJY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRÅTTSJY AS

Who owns BRÅTTSJY AS?

JOAKIM OLSEN EINMO is the largest registered owner, with 100.0%.

Who is the general manager of BRÅTTSJY AS?

Joakim Olsen Einmo is registered as general manager of BRÅTTSJY AS.

Where is BRÅTTSJY AS based?

BRÅTTSJY AS has its business address in Nesna.

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.