biztrac. BETA
COMPANY REGISTER PROFILE
821575532 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

1KONTOR AS

Org. no. 821575532 Limited company (AS) Sandefjord Incorporated 2018 Active
Revenue 2025 NOK 7,000
Operating profit NOK 0
Equity NOK 49,000
Incorporated 2018
Share capital NOK 30,000

1KONTOR AS is registered as a limited company in Sandefjord, Vestfold with organisation number 821575532. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Fremstilling/salg av tjenesten, rådgivning for nybegynnere og nåværende virksomheter og arbeidsmarkedråd for utlendinger.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK 0 in operating profit.

Former names: BUGA AS

Key figures · 2025

Revenue
NOK 7,000
▲ +1052 %
Operating profit
NOK 0
▲ +100 %
Equity
NOK 49,000
▲ +0 %
Est. value
NOK 52,000

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
39.1%
Weak
Equity as a share of total capital

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

Who owns 1KONTOR AS?

1KONTOR AS
NOK 7,000 rev. · NOK 0 profit

1KONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 1KONTOR AS

Who owns 1KONTOR AS?

Jurgita Sliuzaite is the largest registered owner, with 100.0%.

What is the revenue of 1KONTOR AS?

1KONTOR AS had revenue of NOK 7,000 in 2025.

Who is the general manager of 1KONTOR AS?

Jurgita Sliuzaite is registered as general manager of 1KONTOR AS.

Where is 1KONTOR AS based?

1KONTOR AS has its business address in Sandefjord.

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.