BIZTRAC BETA
Retail sale of textiles

NÅL & TRÅD AS

Org. no. 914347866 Limited company (AS) Stord Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −13,000
Equity NOK −794,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−794k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

NÅL & TRÅD AS is registered as a limited company in Stord, Vestland with organisation number 914347866. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Salg av materiell og tilbehør til quilting, bekledning og hobby, samt kursvirksomhet knyttet til dette. Import.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −13,000
Equity
NOK −794,000

Financial health · 2024

Liquidity
2.86
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-93.1%
Weak
Equity as a share of total capital

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

Who owns NÅL & TRÅD AS?

Anne Margrethe Otterå
NÅL & TRÅD AS
NOK 1.4m rev. · NOK −13,000 profit

NÅL & TRÅD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NÅL & TRÅD AS

Who owns NÅL & TRÅD AS?

Anne Margrethe Otterå is the largest registered owner, with 66.7%.

What is the revenue of NÅL & TRÅD AS?

NÅL & TRÅD AS had revenue of NOK 1.4m in 2024.

Who is the general manager of NÅL & TRÅD AS?

Anne Margrethe Otterå is registered as general manager of NÅL & TRÅD AS.

Where is NÅL & TRÅD AS based?

NÅL & TRÅD AS has its business address in Stord.

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.