biztrac. BETA
COMPANY REGISTER PROFILE
817290132 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

SKRÆI AS

Org. no. 817290132 Limited company (AS) Fyresdal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 151,000
Operating profit NOK 30,000
Equity NOK −1.4m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,4 mill kr).

SKRÆI AS is registered as a limited company in Fyresdal, Telemark with organisation number 817290132. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av campingplass, motell, kafé og overnatting.”. The most recent filed accounts, for the 2025 financial year, show NOK 151,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 151,000
▼ −27 %
Operating profit
NOK 30,000
▼ −43 %
Equity
NOK −1.4m
▲ +2 %
Est. value
NOK 229,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
31.8%
Very good
Return on total assets
Solidity
-195187.6%
Weak
Equity as a share of total capital

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

Who owns SKRÆI AS?

SKRÆI AS
NOK 151,000 rev. · NOK 30,000 profit

SKRÆI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRÆI AS

Who owns SKRÆI AS?

Bjørn Veum Seljevold is the largest registered owner, with 100.0%.

What is the revenue of SKRÆI AS?

SKRÆI AS had revenue of NOK 151,000 in 2025.

Who is the general manager of SKRÆI AS?

Bjørn Veum Seljevold is registered as general manager of SKRÆI AS.

Where is SKRÆI AS based?

SKRÆI AS has its business address in Fyresdal.

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.