BIZTRAC BETA
Rental and operating of own or leased real estate

SEVERIN KJÆRSVEI 45 AS

Org. no. 993348880 Limited company (AS) Tønsberg Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 709,000
Operating profit NOK 278,000
Equity NOK 1.6m
Incorporated 2008
Share capital NOK 100,000

SEVERIN KJÆRSVEI 45 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 993348880. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendommer, aksjer, verdipapirer og hva som dermed står i forbindelse, herunder også deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 709,000 in revenue and NOK 278,000 in operating profit.

Key figures · 2025

Revenue
NOK 709,000
Operating profit
NOK 278,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.4%
Very good
Equity as a share of total capital

Who owns SEVERIN KJÆRSVEI 45 AS?

STIG ROALD GRIFFTUN
SEVERIN KJÆRSVEI 45 AS
NOK 709,000 rev. · NOK 278,000 profit

SEVERIN KJÆRSVEI 45 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEVERIN KJÆRSVEI 45 AS

Who owns SEVERIN KJÆRSVEI 45 AS?

STIG ROALD GRIFFTUN is the largest registered owner, with 100.0%.

What is the revenue of SEVERIN KJÆRSVEI 45 AS?

SEVERIN KJÆRSVEI 45 AS had revenue of NOK 709,000 in 2025.

Who is the general manager of SEVERIN KJÆRSVEI 45 AS?

Stig Roald Grifftun is registered as general manager of SEVERIN KJÆRSVEI 45 AS.

Where is SEVERIN KJÆRSVEI 45 AS based?

SEVERIN KJÆRSVEI 45 AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.