biztrac. BETA
COMPANY REGISTER PROFILE
931870912 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Temporary employment agency activities and other human resource provisions

VITAEBEMANNING AS

Org. no. 931870912 Limited company (AS) Bardu Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

VITAEBEMANNING AS is registered as a limited company in Bardu, Troms with organisation number 931870912. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bemanningbyrå, utleie av helsepersonell.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
▲ +0 %
Est. value
NOK 35,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns VITAEBEMANNING AS?

VITAEBEMANNING AS
NOK 0 rev. · NOK 0 profit

VITAEBEMANNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VITAEBEMANNING AS

Who owns VITAEBEMANNING AS?

Kristoffer Pedersen is the largest registered owner, with 100.0%.

What is the revenue of VITAEBEMANNING AS?

VITAEBEMANNING AS had revenue of NOK 0 in 2025.

Who is the general manager of VITAEBEMANNING AS?

Kristoffer Pedersen is registered as general manager of VITAEBEMANNING AS.

Where is VITAEBEMANNING AS based?

VITAEBEMANNING AS has its business address in Bardu.

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.