BIZTRAC BETA
Growing of other non-perennial crops

SPIRO AS

Org. no. 922168784 Limited company (AS) Kvinnherad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −76,000
Equity NOK −406,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

SPIRO AS is registered as a limited company in Kvinnherad, Vestland with organisation number 922168784. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av planter og gartnartenestar, medverka i andre selskap innan same verksemd, samt alt som høyrer naturleg til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −76,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −76,000
Equity
NOK −406,000

Financial health · 2024

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

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

Who owns SPIRO AS?

LATA MARIE AVSNES
SPIRO AS
NOK 7,000 rev. · NOK −76,000 profit

SPIRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPIRO AS

Who owns SPIRO AS?

LATA MARIE AVSNES is the largest registered owner, with 50.0%.

What is the revenue of SPIRO AS?

SPIRO AS had revenue of NOK 7,000 in 2024.

Who is the general manager of SPIRO AS?

Lata Marie Avsnes is registered as general manager of SPIRO AS.

Where is SPIRO AS based?

SPIRO AS has its business address in Dimmelsvik.

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.