biztrac. BETA
COMPANY REGISTER PROFILE
928636925 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Holiday and other short-stay accommodation

TANDSTAD RORBUER AS

Org. no. 928636925 Limited company (AS) Bærum Incorporated 2021 Active
Revenue 2025 NOK 315,000
Operating profit NOK −78,000
Equity NOK −106,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

TANDSTAD RORBUER AS is registered as a limited company in Bærum, Akershus with organisation number 928636925. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bygging og utleie av rorbuer i Sykkylven, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 315,000 in revenue and NOK −78,000 in operating profit.

Key figures · 2025

Revenue
NOK 315,000
▲ +111 %
Operating profit
NOK −78,000
▼ −3348 %
Equity
NOK −106,000
▼ −278 %

Financial health · 2025

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

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

Who owns TANDSTAD RORBUER AS?

TANDSTAD RORBUER AS
NOK 315,000 rev. · NOK −78,000 profit

TANDSTAD RORBUER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANDSTAD RORBUER AS

Who owns TANDSTAD RORBUER AS?

CONSYS AS is the largest registered owner, with 100.0%.

What is the revenue of TANDSTAD RORBUER AS?

TANDSTAD RORBUER AS had revenue of NOK 315,000 in 2025.

Where is TANDSTAD RORBUER AS based?

TANDSTAD RORBUER AS has its business address in Kolsås.

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.