biztrac. BETA
COMPANY REGISTER PROFILE
917917132 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Combined facilities support activities

STRANDSERVICE AS

Org. no. 917917132 Limited company (AS) Porsanger Incorporated 2016 Active
Revenue 2025 NOK 94,000
Operating profit NOK −184,000
Equity NOK −129,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−129k kr).

STRANDSERVICE AS is registered as a limited company in Porsanger, Finnmark with organisation number 917917132. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av vaktmestertjenester og snøbrøyting. Transport av materiell og utstyr til turister. Sauehold.”. The most recent filed accounts, for the 2025 financial year, show NOK 94,000 in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 94,000
▼ −79 %
Operating profit
NOK −184,000
▼ −62 %
Equity
NOK −129,000
▼ −337 %

Financial health · 2025

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
-64.4%
Not satisfactory
Return on total assets
Solidity
-65.1%
Weak
Equity as a share of total capital

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

Who owns STRANDSERVICE AS?

STRANDSERVICE AS
NOK 94,000 rev. · NOK −184,000 profit

STRANDSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDSERVICE AS

Who owns STRANDSERVICE AS?

Jan Erik Strand is the largest registered owner, with 100.0%.

What is the revenue of STRANDSERVICE AS?

STRANDSERVICE AS had revenue of NOK 94,000 in 2025.

Where is STRANDSERVICE AS based?

STRANDSERVICE AS has its business address in Skoganvarre.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.