BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

HASA SERVICE AS

Org. no. 911585693 Limited company (AS) Fitjar Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −297,000
Equity NOK 3.1m
Incorporated 2013
Share capital NOK 30,000

Signals

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

HASA SERVICE AS is registered as a limited company in Fitjar, Vestland with organisation number 911585693. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av arbeidskraft, reparasjon av skip og båter samt alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −297,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −297,000
Equity
NOK 3.1m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns HASA SERVICE AS?

SANDRA STECKA
HASA SERVICE AS
NOK 1.1m rev. · NOK −297,000 profit

HASA SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HASA SERVICE AS

Who owns HASA SERVICE AS?

SANDRA STECKA is the largest registered owner, with 100.0%.

What is the revenue of HASA SERVICE AS?

HASA SERVICE AS had revenue of NOK 1.1m in 2025.

Who is the general manager of HASA SERVICE AS?

Sandra Stecka is registered as general manager of HASA SERVICE AS.

Where is HASA SERVICE AS based?

HASA SERVICE AS has its business address in Fitjar.

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.