biztrac. BETA
COMPANY REGISTER PROFILE
929978226 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SALTBUVIKA AS

Org. no. 929978226 Limited company (AS) Levanger Incorporated 2022 Active
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −15,000
Incorporated 2022
Share capital NOK 40,000

Signals

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

SALTBUVIKA AS is registered as a limited company in Levanger, Trøndelag with organisation number 929978226. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Utvikling, forvaltning, utleie, kjøp og salg av eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▲ +5 %
Equity
NOK −15,000
▼ −1269 %

Financial health · 2025

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

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

Who owns SALTBUVIKA AS?

SALTBUVIKA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALTBUVIKA AS

Who owns SALTBUVIKA AS?

Aksel Ryggvik is the largest registered owner, with 25.0%.

What is the revenue of SALTBUVIKA AS?

SALTBUVIKA AS had revenue of NOK 0 in 2025.

Who is the general manager of SALTBUVIKA AS?

Roger Bremseth is registered as general manager of SALTBUVIKA AS.

Where is SALTBUVIKA AS based?

SALTBUVIKA AS has its business address in Åsen.

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.